Avaya Operational Analyst Installation and Configuration

Transcription

1 Avaya Operational Analyst Installation and Configuration Release 7.3.x Issue 3 February 2017

2 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 "Documentation" means information published in varying mediums which may include product information, operating instructions and performance specifications that are generally made available to users of products. Documentation does not include marketing materials. Avaya shall not be responsible for any modifications, additions, or deletions to the original published version of Documentation unless such modifications, additions, or deletions were performed by or on the express behalf of Avaya. End User agrees 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 websites referenced within this site or Documentation 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 Avaya hardware and software. 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 website: under the link "Warranty & Product Lifecycle" or such successor site as designated by Avaya. Please note that if You acquired the product(s) from an authorized Avaya Channel Partner outside of the United States and Canada, the warranty is provided to You by said Avaya Channel Partner and not by Avaya. "Hosted Service" means an Avaya hosted service subscription that You acquire from either Avaya or an authorized Avaya Channel Partner (as applicable) and which is described further in Hosted SAS or other service description documentation regarding the applicable hosted service. If You purchase a Hosted Service subscription, the foregoing limited warranty may not apply but You may be entitled to support services in connection with the Hosted Service as described further in your service description documents for the applicable Hosted Service. Contact Avaya or Avaya Channel Partner (as applicable) for more information. Hosted Service THE FOLLOWING APPLIES ONLY IF YOU PURCHASE AN AVAYA HOSTED SERVICE SUBSCRIPTION FROM AVAYA OR AN AVAYA CHANNEL PARTNER (AS APPLICABLE), THE TERMS OF USE FOR HOSTED SERVICES ARE AVAILABLE ON THE AVAYA WEBSITE, UNDER THE LINK "Avaya Terms of Use for Hosted Services" OR SUCH SUCCESSOR SITE AS DESIGNATED BY AVAYA, AND ARE APPLICABLE TO ANYONE WHO ACCESSES OR USES THE HOSTED SERVICE. BY ACCESSING OR USING THE HOSTED SERVICE, OR AUTHORIZING OTHERS TO DO SO, YOU, ON BEHALF OF YOURSELF AND THE ENTITY FOR WHOM YOU ARE DOING SO (HEREINAFTER REFERRED TO INTERCHANGEABLY AS "YOU" AND "END USER"), AGREE TO THE TERMS OF USE. IF YOU ARE ACCEPTING THE TERMS OF USE ON BEHALF A COMPANY OR OTHER LEGAL ENTITY, YOU REPRESENT THAT YOU HAVE THE AUTHORITY TO BIND SUCH ENTITY TO THESE TERMS OF USE. IF YOU DO NOT HAVE SUCH AUTHORITY, OR IF YOU DO NOT WISH TO ACCEPT THESE TERMS OF USE, YOU MUST NOT ACCESS OR USE THE HOSTED SERVICE OR AUTHORIZE ANYONE TO ACCESS OR USE THE HOSTED SERVICE. Licenses THE SOFTWARE LICENSE TERMS AVAILABLEON THE AVAYA WEBSITE, UNDER THE LINK "AVAYA SOFTWARE LICENSE TERMS (Avaya Products)" OR SUCH SUCCESSOR SITE AS DESIGNATED BY AVAYA, ARE APPLICABLE TO ANYONE WHO DOWNLOADS, USES AND/OR INSTALLS AVAYA SOFTWARE, PURCHASED FROM AVAYA INC., ANY AVAYA AFFILIATE, OR AN AVAYA CHANNEL PARTNER (AS APPLICABLE) UNDER A COMMERCIAL AGREEMENT WITH AVAYA OR AN AVAYA CHANNEL PARTNER. 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 CHANNEL PARTNER; 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 You a license within the scope of the license types described below, with the exception of Heritage Nortel Software, for which the scope of the license is detailed below. Where the order documentation does not expressly identify a license type, the applicable license will be a Designated System License. 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 You. " Software" means computer programs in object code, provided by Avaya or an Avaya Channel Partner, whether as stand-alone products, pre-installed on hardware products, and any upgrades, updates, patches, bug fixes, or modified versions thereto. "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. "Instance" means a single copy of the Software executing at a particular time: (i) on one physical machine; or (ii) on one deployed software virtual machine ("VM") or similar deployment. License type(s) Designated System(s) License (DS). End User may install and use each copy or an Instance of the Software only on a number of Designated Processors up to the number indicated in the order. Avaya may require the Designated Processor(s) to be identified in the order by type, serial number, feature key, Instance, location or other specific designation, or to be provided by End User to Avaya through electronic means established by Avaya specifically for this purpose. Concurrent User License (CU). End User may install and use the Software on multiple Designated Processors or one or more Servers, so long as only the licensed number of Units are accessing and using the Software at any given time. A "Unit" means the unit on which Avaya, at its sole discretion, bases the pricing of its licenses and can be, without limitation, an agent, port or user, an or voice mail account in the name of a person or corporate function (e.g., webmaster or helpdesk), or a directory entry in the administrative database utilized by the Software that permits one user to interface with the Software. Units may be linked to a specific, identified Server or an Instance of the Software. Heritage Nortel Software "Heritage Nortel Software" means the software that was acquired by Avaya as part of its purchase of the Nortel Enterprise Solutions Business in December The Heritage Nortel Software is the software contained within the list of Heritage Nortel Products located at under the link "Heritage Nortel Products," or such successor site as designated by Avaya. For Heritage Nortel Software, Avaya grants Customer a license to use Heritage Nortel Software provided hereunder solely to the extent of the authorized activation or authorized usage level, solely for the purpose specified in the Documentation, and solely as embedded in, for execution on, or for communication with Avaya equipment. Charges for Heritage Nortel Software may be based on extent of activation or use authorized as specified in an order or invoice. Copyright Except where expressly stated otherwise, no use should be made of materials on this site, the Documentation, Software, Hosted Service, or hardware provided by Avaya. All content on this site, the documentation, Hosted Service, and the product 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 unless expressly authorized by Avaya. 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. Virtualization The following applies if the product is deployed on a virtual machine. Each product has its own ordering code and license types. Note that each Instance of a product must be separately licensed and ordered. For example, if the end user customer or Avaya Channel Partner would like to install two Instances of the same type of products, then two products of that type must be ordered. Third party components "Third Party Components" mean certain software programs or portions thereof included in the Software or Hosted Service may contain software (including

3 open source software) distributed under third party agreements ("Third Party Components"), which contain terms regarding the rights to use certain portions of the Software ("Third Party Terms"). As required, information regarding distributed Linux OS source code (for those products that have distributed Linux OS source code) and identifying the copyright holders of the Third Party Components and the Third Party Terms that apply is available in the products, Documentation or on Avaya's website at: or such successor site as designated by Avaya. The open source software license terms provided as Third Party Terms are consistent with the license rights granted in these Software License Terms, and may contain additional rights benefiting You, such as modification and distribution of the open source software. The Third Party Terms shall take precedence over these Software License Terms, solely with respect to the applicable Third Party Components, to the extent that these Software License Terms impose greater restrictions on You than the applicable Third Party Terms. The following applies if the H.264 (AVC) codec is distributed with the product. THIS PRODUCT IS LICENSED UNDER THE AVC PATENT PORTFOLIO LICENSE FOR THE PERSONAL USE OF A CONSUMER OR OTHER USES IN WHICH IT DOES NOT RECEIVE REMUNERATION TO (i) ENCODE VIDEO IN COMPLIANCE WITH THE AVC STANDARD ("AVC VIDEO") AND/OR (ii) DECODE AVC VIDEO THAT WAS ENCODED BY A CONSUMER ENGAGED IN A PERSONAL ACTIVITY AND/OR WAS OBTAINED FROM A VIDEO PROVIDER LICENSED TO PROVIDE AVC VIDEO. NO LICENSE IS GRANTED OR SHALL BE IMPLIED FOR ANY OTHER USE. ADDITIONAL INFORMATION MAY BE OBTAINED FROM MPEG LA, L.L.C. SEE Service Provider THE FOLLOWING APPLIES TO AVAYA CHANNEL PARTNER'S HOSTING OF AVAYA PRODUCTS OR SERVICES. THE PRODUCT OR HOSTED SERVICE MAY USE THIRD PARTY COMPONENTS SUBJECT TO THIRD PARTY TERMS AND REQUIRE A SERVICE PROVIDER TO BE INDEPENDENTLY LICENSED DIRECTLY FROM THE THIRD PARTY SUPPLIER. AN AVAYA CHANNEL PARTNER'S HOSTING OF AVAYA PRODUCTS MUST BE AUTHORIZED IN WRITING BY AVAYA AND IF THOSE HOSTED PRODUCTS USE OR EMBED CERTAIN THIRD PARTY SOFTWARE, INCLUDING BUT NOT LIMITED TO MICROSOFT SOFTWARE OR CODECS, THE AVAYA CHANNEL PARTNER IS REQUIRED TO INDEPENDENTLY OBTAIN ANY APPLICABLE LICENSE AGREEMENTS, AT THE AVAYA CHANNEL PARTNER'S EXPENSE, DIRECTLY FROM THE APPLICABLE THIRD PARTY SUPPLIER. WITH RESPECT TO CODECS, IF THE AVAYA CHANNEL PARTNER IS HOSTING ANY PRODUCTS THAT USE OR EMBED THE G.729 CODEC, H.264 CODEC, OR H.265 CODEC, THE AVAYA CHANNEL PARTNER ACKNOWLEDGES AND AGREES THE AVAYA CHANNEL PARTNER IS RESPONSIBLE FOR ANY AND ALL RELATED FEES AND/OR ROYALTIES. THE G.729 CODEC IS LICENSED BY SIPRO LAB TELECOM INC. SEE THE H.264 (AVC) CODEC IS LICENSED UNDER THE AVC PATENT PORTFOLIO LICENSE FOR THE PERSONAL USE OF A CONSUMER OR OTHER USES IN WHICH IT DOES NOT RECEIVE REMUNERATION TO: (I) ENCODE VIDEO IN COMPLIANCE WITH THE AVC STANDARD ("AVC VIDEO") AND/OR (II) DECODE AVC VIDEO THAT WAS ENCODED BY A CONSUMER ENGAGED IN A PERSONAL ACTIVITY AND/OR WAS OBTAINED FROM A VIDEO PROVIDER LICENSED TO PROVIDE AVC VIDEO. NO LICENSE IS GRANTED OR SHALL BE IMPLIED FOR ANY OTHER USE. ADDITIONAL INFORMATION FOR H.264 (AVC) AND H.265 (HEVC) CODECS MAY BE OBTAINED FROM MPEG LA, L.L.C. SEE Compliance with Laws You acknowledge and agree that it is Your responsibility for complying with any applicable laws and regulations, including, but not limited to laws and regulations related to call recording, data privacy, intellectual property, trade secret, fraud, and music performance rights, in the country or territory where the Avaya product is used. 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 Toll Fraud intervention If You suspect that You are being victimized by Toll Fraud and You need technical assistance or support, call Technical Service Center Toll Fraud Intervention Hotline at for the United States and Canada. For additional support telephone numbers, see the Avaya Support website: or such successor site as designated by Avaya. Security Vulnerabilities Information about Avaya's security support policies can be found in the Security Policies and Support section of Suspected Avaya product security vulnerabilities are handled per the Avaya Product Security Support Flow ( Trademarks The trademarks, logos and service marks ("Marks") displayed in this site, the Documentation, Hosted Service(s), and product(s) provided by Avaya are the registered or unregistered Marks of Avaya, its affiliates, its licensors, its suppliers, or other third parties. Users are not permitted to use such Marks without prior written consent from Avaya or such third party which may own the Mark. Nothing contained in this site, the Documentation, Hosted Service(s) and product(s) should be construed as granting, by implication, estoppel, or otherwise, any license or right in and to the Marks without the express written permission of Avaya or the applicable third party. Avaya is a registered trademark of Avaya Inc. All non-avaya trademarks are the property of their respective owners. Linux is the registered trademark of Linus Torvalds in the U.S. and other countries. Downloading Documentation For the most current versions of Documentation, see the Avaya Support website: or such successor site as designated by Avaya. Contact Avaya Support See the Avaya Support website: for product or Hosted Service notices and articles, or to report a problem with your Avaya product or Hosted Service. For a list of support telephone numbers and contact addresses, go to the Avaya Support website: (or such successor site as designated by Avaya), scroll to the bottom of the page, and select Contact Avaya Support.

4 Contents Chapter 1: Introduction Purpose Intended audience Document changes since last issue Related resources Documentation Training Viewing Avaya Mentor videos Support Chapter 2: Preparing for installation Software on the Avaya OA DVD Server applications Client applications Data collection applications Third-party applications Path definitions Windows path definitions Solaris SPARC path definitions RHEL path definitions AIX path definitions Security for UNIX platforms Security for Windows platforms Support for Oracle 12.1c database Verifying the Oracle Home location on Windows Verifying the Oracle Home location on Oracle Solaris Preinstallation checklist Subsystem and client software installation considerations Avaya OA installation examples Chapter 3: Installing Avaya OA components Security for Unix platforms Security for Windows platforms Installation checklist Before you begin the installation Installing Avaya OA components on a Windows platform Verifying the Avaya OA installation on Windows platform Configuring OA Administration client on Microsoft Windows Changing Local Security Policy Installation and Configuration February

5 Launching Microsoft Internet Explorer in Administrator mode Installing Avaya OA components on a Solaris SPARC platform Verifying Avaya OA installation on Solaris SPARC platform Installing Avaya OA components on an AIX platform Verifying the Avaya OA installation on AIX platform Installing Avaya OA components on a CMS server - Solaris SPARC Installing Avaya OA components - Solaris SPARC Configuring time zone offsets Installing Informix client SDK library- Solaris SPARC for CMS R16.x and R17.x Installing Informix client SDK library on Oracle Solaris for CMS Installing Avaya OA components on a CMS server for RHEL Installing Avaya OA components - RHEL Verifying the Avaya OA installation on the CMS server with RHEL platform Configuring time zone offsets Installing Informix client SDK library on RHEL for CMS 16.x and 17.x Installing Informix client SDK library on RHEL for CMS Uninstalling Informix client SDK library Uninstalling Informix client SDK library on CMS 16.x and 17.x Uninstalling Informix client SDK library on CMS Installing and testing the Report client Installing the Report client support files for OA and later Installing the Report client support files for OA and earlier OA Release Basic Reports on Microsoft Windows 7 (64 bit) Configuring Microsoft Internet Explorer on Microsoft Windows 7 and Installing the reporting support files Verifying the installation of Reporting files Running a test report Completing the installation Setting up remote access Configuring the NumDSWorkerThreads parameter on the Report servers Configuring the SMPOptLevel parameter on the TimesTen server Configuring Cognos for multibyte language support Chapter 4: Configuring Avaya OA subsystems and event collectors Administration client options Customizing the Administration client Setting the archive time zone definition Starting the Avaya OA Administration client Adding a Real-time subsystem Installation and Configuration February

6 Adding an Avaya IC Source subsystem Adding a CMS subsystem Adding an ACD Source subsystem Adding a Report subsystem Administering the Source-EC (Event Collector) server Determining Real-time System ID and Data Manager Host Administering the Event Collector server Administering the Source-EC Bridge (Event Collector Bridge) Completing initial administration Configuring SSL for OA Configuring SSL for Windows for OA and earlier Configuring SSL for Windows for OA and later Restarting the Tomcat to finish the configuration Configuring SSL for Solaris or AIX on OA and earlier Configuring SSL for Solaris on OA and later Generate the KeyStore file Configuring Tomcat for using the KeyStore file Configure OA to work with SSL Restart tomcat to finish the configuration Changing the port number of the Tomcat server Chapter 5: Making changes to installed Avaya OA components Preparation checklist Stopping or starting processes and services before making changes Stopping processes and services Starting processes and services Adding Avaya OA components License key considerations Interactions Adding Avaya OA components Adding Avaya OA components on the CMS server with RHEL platform Completing an addition to Avaya OA Repairing Avaya OA components Considerations when doing a repair Repairing Avaya OA components Repairing Avaya OA components on the CMS server with RHEL platform Completing a repair to Avaya OA software Moving subsystems General guidelines Installation and Configuration February

7 Example of moving subsystems Moving the Real-time subsystem Moving the Event Collector subsystem Moving the Event Collector Bridge subsystem Moving CMS and ACD subsystems Moving the Report subsystem Changing subsystem attributes Example for changing a domain name Changing the Historical subsystem system name or IP address Changing the naming service port number Removing Avaya OA components Considerations when removing OA components Removing Avaya OA components from Windows system Removing Avaya OA software from Solaris SPARC system Removing Avaya OA software from Red Hat Enterprise Linux (RHEL) system. 328 Removing Avaya OA software from the AIX system Chapter 6: Troubleshooting an installation Incorrect OS and database installation Diagnosing installation problems Installation failure after changing the domain name Processes not running Data not transferred or collected Missing files Subsystems not installed Report client installation fails to work Unable to install Report client files Report access failure Administration client authorization failures Password changes Display problems with AIX Corruption in AIX terminal windows Domain controller loses connection Appendix A: Using latest version of Oracle JRE for Reporting Client for OA Security Restrictions introduced in JRE 1.7/ Appendix B: Changing the Cognos installation Prerequisites Installation and Configuration February

8 Changing the Cognos installation Appendix C: Remote installation of CMS data collection software Solaris SPARC Red Hat Enterprise Linux (RHEL) Installation and Configuration February

9 Chapter 1: Introduction Purpose The purpose of this guide is to provide detailed instructions for installing Avaya Operational Analyst (OA). Intended audience This information is for Avaya Global Services personnel, business partners, and customers who install Avaya OA software. Document changes since last issue The following sections have changed in this document since the last issue: RHEL path definitions on page 22 Installing Avaya OA components - Solaris SPARC on page 117 Installing Informix client SDK library on Oracle Solaris for CMS 18 on page 128 Installing Avaya OA components on a CMS server for RHEL on page 132 Verifying the Avaya OA installation on the CMS server with RHEL platform on page 139 Installing Informix client SDK library on RHEL for CMS 16.x and 17.x on page 145 Installing Informix client SDK library on RHEL for CMS 18 on page 149 Starting processes and services on a Windows server on page 213 Starting processes on a Solaris SPARC server on page 214 Starting processes on RHEL server on page 214 Starting processes on an AIX server on page 215 Adding Avaya OA components on the CMS server with RHEL platform on page 238 To complete an addition to the RHEL system on page 252 Installation and Configuration February

10 Chapter 1: Introduction Repairing Avaya OA components on the CMS server with RHEL platform on page 272 Completing a repair to Avaya OA software on page 276 Removing Avaya OA software from Red Hat Enterprise Linux (RHEL) system on page 328 Remote installation of CMS data collection software on page 375 Avaya provides the following DVDs on page Installation and Configuration February 2017

11 Related resources Related resources Documentation See the following related documents at Title Description Audience Avaya Interaction Center and Avaya Operational Analyst Overview and Specification This document describes tested Interaction Center (IC) and Operational Analyst(OA) characteristics and capabilities, including feature descriptions, interoperability, performance specifications, and security and licensing requirements. Customers Administrators Finding documents on the Avaya Support website Use this procedure to find product documentation on the Avaya Support website. 1. Use a browser to navigate to the Avaya Support website at 2. At the top of the screen, enter your username and password and click Login. 3. Click Documents. 4. In the Enter your Product Here search box, type the product name and then select the product from the drop-down list. 5. If there is more than one release, select the appropriate release number from the Choose Release drop-down list. 6. Use the Content Type filter on the left to select the type of document you are looking for, or click Select All to see a list of all available documents. For example, if you are looking for user guides, select User Guides in the Content Type filter. Only documents in the selected category will appear in the list of documents. 7. Click Enter. Installation and Configuration February

12 Chapter 1: Introduction Training The following courses are available on the Avaya Learning website at In the Search field, enter the course code, and click Go to search for the course. Course Code Course Title ATC01175WEN IC and OA Overview ATC01176IEN Interaction Center Administration and Configuration AUCC The Basics of Operational Analyst Part 1. AUCC The Basics of Operational Analyst Part 2. ATC01171IEN Operational Analyst Planning and Implementation. Viewing Avaya Mentor videos Avaya Mentor videos provide technical content on how to install, configure, and troubleshoot Avaya products. Videos are available on the Avaya Support website, listed under the video document type, and on the Avaya-run channel on YouTube. To find videos on the Avaya Support website, go to and perform one of the following actions: - In Search, type Avaya Mentor Videos to see a list of the available videos. - In Search, type the product name. On the Search Results page, select Video in the Content Type column on the left. To find the Avaya Mentor videos on YouTube, go to and perform one of the following actions: - Enter a key word or key words in the Search Channel to search for a specific product or topic. - Scroll down Playlists, and click the name of a topic to see the available list of videos posted on the website. Videos are not available for all products. 12 Installation and Configuration February 2017

13 Support Support Go to the Avaya Support website at for the most up-to-date documentation, product notices, and knowledge articles. You can also search for release notes, downloads, and resolutions to issues. Use the online service request system to create a service request. Chat with live agents to get answers to questions, or request an agent to connect you to a support team if an issue requires additional expertise. Installation and Configuration February

14 Chapter 1: Introduction 14 Installation and Configuration February 2017

15 Chapter 2: Preparing for installation Before you begin the Avaya OA installation, read the following sections and perform the following procedures in these sections: Software on the Avaya OA DVD on page 16 Path definitions on page 20 Security for UNIX platforms on page 23 Preinstallation checklist on page 25 Subsystem and client software installation considerations on page 28 Avaya OA installation examples on page 30 Avaya provides the following DVDs Avaya OA DVD Cognos Impromptu and powerplay user Cognos Transformation server Software The structure is: 1. COGNOS SFTW IMPROMPTU ADMIN R COGNOS SFTW DOCUMENATION R COGNOS SFTW POWERPLAY USER/CLIENT R COGNOS SFTW POWERPLAY ENT SRVR ADMIN R COGNOS SFTW IMPROMPTU WEB REPORT R COGNOS SFTW IMPROMPTU WEB REPORT ADMIN R7.4 The structure is: COGNOS SFTW POWERPLAY TRANS SRVR R7.4 The Important: Congnos software packages were available with OA 7.3. From OA onwards the above packages are no longer available and not supported.! Important: Advanced Reports are End of Sale (EoS) and End of Manufacturing Support. For more details, see the EoS notification at documents/ Content present in this document pertaining to 'Advanced Reports' is kept for reference purpose for those who have implemented advanced reports prior to EoS and must not be referenced for any deployments post EoS. Installation and Configuration February

16 Chapter 2: Preparing for installation Software on the Avaya OA DVD The Avaya OA software DVD includes the following: Server applications on page 16 - Historical subsystem - Real-time subsystem - Report subsystem Client applications on page 17 - Administration - Basic Reports - Advanced Reports - Data API Utility Data collection applications on page 19 - Source-CMS - Source-EC (Event Collector) - Source-EC Bridge (Event Collector Bridge) Third-party applications on page 20 - Java Runtime Environment (JRE) - TimesTen Database For OA on CMS RHEL, only the following applications are applicable: - Data API Utility - Source-CMS - Java Runtime Environment (JRE) Server applications Avaya OA server components consist of core (common) software applications. This core is automatically and transparently installed when required, based on which components of Avaya OA are installed. 16 Installation and Configuration February 2017

17 Software on the Avaya OA DVD Historical subsystem The Historical subsystem analyzes the data in the database. For list of supported databases see Avaya Operational Analyst Release 7.3.x Installation Planning and Prerequisites. Real-time subsystem The Real-time subsystem processes the active work items in the real-time database. This release of Avaya OA requires the TimesTen Real-time database software. The installation of this software happens automatically when you select the Real-time subsystem while installing Avaya OA. Report subsystem The Report subsystem and Advanced Report subsystem provides the Web-based report framework necessary to run Basic Reports or Advanced Reports. Client applications Avaya OA client components are applications that are active on clients to help you manage many of the Avaya OA functions. You can install these applications on hardware and on software as described in Avaya Operational Analyst Release 7.3.x Installation Planning and Prerequisites. Administration The Administration client is an Avaya OA utility that lets you manage many of the Avaya OA components and operations. You can manage these components and operations using a graphical user interface running under Microsoft Internet Explorer. For list of supported Microsoft Internet Explorer see Avaya Operational Analyst Release 7.3.x Installation Planning and Prerequisites. You can install administration client on any or all Windows-based OA or IC servers or on a standalone Windows-based workstation. Basic Reports The Report client lets you view the OA Basic Reports and the OA Tabular Reports. You can install the Report client on standalone Windows-based workstations. Important:! Important: When installing the Report client, decide on the following: Installation and Configuration February

18 Chapter 2: Preparing for installation - Do not install the Report client on any system running Microsoft Windows Server 2008 R2 (Standard and Enterprise edition) or Microsoft Windows Server 2012 Standard edition. - Do not install the Report client coresident on any IC servers. - For different software requirements, running Basic Report along with other OA client applications is not supported. - For performance and different hardware and software requirement reasons, running the Basic Reports on the report server is not supported. For installing the latest version of Operational Analyst Reporting software, customers who are on Microsoft Windows 7 (x64 bit), and Microsoft Windows 8.1 and have only the OA Reporting client installed on that system of the earlier Service Pack must perform the following: 1. Upgrade the Internet Explorer to one of the supported browser version. For details see Avaya Interaction Center Release 7.3.x Installation Planning and Prerequisites. 2. Uninstall the earlier/older Basic Reporting Client as well as the older JRE. 3. Reinstall the supported JRE for OA Reporting client. For details see Avaya Interaction Center Release 7.3.x Installation Planning and Prerequisites. 4. Reinstall OA Reporting client supporting files if you are using OA The Install Reporting Support Files option is not applicable to OA The support files are automatically installed when the OA Reporting client is launched. 5. Ensure you do not have any other OA applications running on the system. Customer who have IE 9,10 or 11 installed on Windows 7 (x64) without any prior OA reporting component installed, can follow steps in the next section for viewing OA Reports Advanced Reports. Advanced Reports require Cognos Impromptu Administrator and PowerPlay Transformation Server to view non web-based reports. You use the Transformer to generate the cube, and use PowerPlay to view the cube. To view the web version of the reports, you must install Cognos Impromptu Web Reports and Cognos PowerPlay Enterprise Server. This installation also automatically installs Cognos Upfront. You can install these applications from the Cognos DVD that comes with the Avaya OA software. For more information, see the Cognos documentation. You must install Advanced Reporting on the same server as the Cognos Impromptu Administrator. For Advanced reporting, Avaya OA uses COGNOS 7.4. COGNOS 7.4 runs only on the 32-bit Windows system and does not have a compatible version that can run on the 64-bit system. However, Avaya OA only supports Windows Server 2008 R2 and Windows Server 2012 R2. Therefore, you cannot use Advanced reporting on Windows Server 2008 R2, Windows Server 2012 R2, Solaris, or AIX. The Advanced Report sub system only functions on Microsoft Windows XP. 18 Installation and Configuration February 2017

19 Software on the Avaya OA DVD Since, Microsoft Windows XP support is dropped in OA 7.3.3, Advanced Report sub system is no longer supported from OA onwards. The Cognos catalog connects with the database from the system running Cognos, and requires the appropriate database client. PowerPlay requires access to predefined PowerPlay cubes. Each user that wants to run PowerPlay must have access to the cubes. If you do not install the cubes on the same system as PowerPlay, you need LAN access from the PowerPlay system through a mapped drive to the location of the PowerPlay cubes. Data API Utility OA offers a Data API Utility for exporting data from the real-time and historical databases to support work force management software. Data collection applications You must load Avaya OA data collection applications on IC or Call Management System (CMS) servers. The data collection applications collect data for reporting through Avaya OA. Source-CMS subsystem The system loads Source-CMS subsystem on the CMS server. This subsystem collects and sends data to the OA historical server. Source-EC (Event Collector) subsystem The system loads Source-EC (Event Collector) subsystem on an IC server. This subsystem collects data from the ADU servers and sends the data to the OA Real-time subsystem. Source-EC Bridge (Event Collector Bridge) subsystem The system loads Source-EC Bridge (Event Collector Bridge) subsystem on an IC server. This subsystem collects data from Avaya Business Advocate. Installation and Configuration February

20 Chapter 2: Preparing for installation Third-party applications Oracle Java Runtime Environment (JRE) You require JRE for Java-based applications, such as Avaya OA Administration client. JRE provides the environment that enables these applications to run. The system automatically installs JRE during Avaya OA installation on servers. However, you must manually install JRE when installing the Report client support files on a Windows system. For more information, see Avaya Operational Analyst Release 7.3.x Installation Planning and Prerequisites. Using any other version of JRE might have an impact on customer applications on Windows systems if the applications require a different version. For using the latest version of JRE, see Using latest version of Oracle JRE for Reporting Client for OA on page 349. TimesTen Real-time database This software provides the memory-resident database used by the OA Real-time subsystem to store real-time operational information about the contact center. The system automatically installs TimesTen when you install the Real-time subsystem. Path definitions It is important to understand the path definitions for the different operating systems: Windows path definitions on page 21 Solaris SPARC path definitions on page 21 RHEL path definitions on page 22 AIX path definitions on page 22 Important:! Important: If you choose to install Avaya OA in locations other than the defaults recommended by Avaya, this affects all examples of install locations noted in this document. 20 Installation and Configuration February 2017

21 Path definitions Windows path definitions The following variable is used in this document to represent the installation path for most Avaya OA software on Windows: %PABASE% For example, the location for a file in that path is as follows: %PABASE%\stumbras\tomcat\work\localhost_8080 The following is the default installation path Avaya OA uses on a Windows server: c:\program Files(x86)\Avaya\BI When installing Avaya OA, the system does not display the BI part of the path when the default path is shown in the Destination dialog box. This part is added as part of the installation. The following variable is used in this document to represent the installation path for EC Server and EC Bridge software on Windows: %AVAYA_IC73_HOME%\bin The following is the default installation path IC uses on a Windows server: c:\avaya\ic73 Solaris SPARC path definitions The following variable is used in this document to represent the installation path for most Avaya OA software on Solaris: $PABASE For example, the location for a directory in that path is shown as follows: $PABASE/data/log Depending on the installation of the OS and the creation of the file systems, the following is the default installation path Avaya OA uses on a Solaris server: /export/home/biadmin/bi When installing Avaya OA, the system does not display the BI part of the path when the default path is shown in the Destination dialog box. This part is added as part of the installation. Installation and Configuration February

22 Chapter 2: Preparing for installation The following variables are used in this document to represent the installation path for EC Server software and libraries on Solaris: $AVAYA_IC73_HOME/bin $AVAYA_IC73_HOME/lib Depending on the installation of the OS and creation of the file systems, the following is the default installation path IC uses on a Solaris server: /opt/avaya/ic73 RHEL path definitions The following variable is used in this document to represent the installation path for most Avaya OA software on RHEL: $PABASE For example, the location for a directory in that path is as follows: $PABASE/data/log Depending on the installation of the OS and creation of the file systems, the following is the default installation path Avaya OA uses on a RHEL server: /export/home/biadmin/bi When installing Avaya OA, the system displays the BI part of the path when the default path is shown in the Destination dialog box. This part is added as part of the installation. AIX path definitions The following variable is used in this document to represent the installation path for most Avaya OA software on AIX: $PABASE For example, the location for a directory in that path is as follows: $PABASE/data/log Depending on the installation of the OS and creation of the file systems, the following is the default installation path Avaya OA uses on an AIX server: /home/biadmin/bi 22 Installation and Configuration February 2017

23 Security for UNIX platforms When installing Avaya OA, the system displays the BI part of the path when the default path is shown in the Destination dialog box. This part is added as part of the installation. The following variables are used in this document to represent the installation path for EC Server software and libraries on AIX: $AVAYA_IC73_HOME/bin $AVAYA_IC73_HOME/lib Depending on the installation of the OS and creation of the file systems, the following is the default installation path IC uses on an AIX server: /usr/avaya/ic73 Security for UNIX platforms Avaya recommends that users avoid running Avaya software as the root user for security reasons. This does not apply to the installation software itself, which must be run as the root user. Security for Windows platforms Avaya recommends that users avoid running Avaya software as the administrator user for security reasons. This does not apply to the installation software itself, which must be run as an administrator user. Support for Oracle 12.1c database Beginning with Oracle database release 11gR2, Oracle 32-bit libraries are no longer shipped with the 64-bit Oracle database server or with the 64-bit Oracle database client media. Installation and Configuration February

24 Chapter 2: Preparing for installation From OA 7.3.3, it is mandatory to install Oracle Client (32 bit) for co-resident as well as distributed/backend Historical database setups. The OA Installer requires the Oracle Client Home as one of the Input values irrespective of the Oracle DB Server version currently being used. Only the Admin type and Runtime type of Oracle Client installation (32 bit) is certified for OA on both Microsoft Windows and Oracle Solaris platform. - Applicable to all the supported Oracle Version 10.x, 11.x, 12.1c and for supported platforms (All Windows and Solaris 10) The Oracle Client Home would be a mandatory parameter to be specified by the customer for following cases: - Fresh Installation of OA and Historical is checked for installation (co-resident). - Fresh Installation of OA and Historical is checked for installation (backend/distributed). - OA upgrade from an earlier version of OA where Historical was a previously installed component. - OA Installer reads the existing value of oraclehome attribute from the server.properties file and pre-populates the field where Oracle Home for client is specified. You must verify the path and change it (if needed) to now point to the correct location. - When running a repair install on OA where Historical is checked for re-installation, the Oracle Client Home field is pre-populated and you do not need to modify the Oracle Client Home path, if unchanged from previous installation. Verifying the Oracle Home location on Windows You can verify the Oracle_Home location on Microsoft Windows Server 2008 R2 (Standard and Enterprise edition) and Microsoft Windows Server 2012 Standard edition from the Registry. The location of ORACLE_HOME in the registry is: HKEY_LOCAL_MACHINE\SOFTWARE\ Wow6432Node\ORACLE Verifying the Oracle Home location on Oracle Solaris You can use the orainventory location to determine the location of the Oracle Client Home path. 1. Open the inventory.xml file located at: /home/oracle/orainventory/contentsxml/ 2. If orainventory directory does not exist in the above path, search for the orainventory in the root directory location. Search for the element named HOME in the inventory.xml file. 24 Installation and Configuration February 2017

25 Preinstallation checklist Preinstallation checklist Before you install Avaya OA, verify that the following prerequisites are complete: Procedure For a configuration that includes Avaya IC, verify whether the Avaya IC components are installed, are configured, and are running. Verify the installation before you install, configure, and run the Avaya OA components. For more information, see: Avaya Interaction Center Release 7.3.x Installation Planning and Prerequisites Avaya Interaction Center Release 7.3.x Installation and Configuration Verify that the customer has obtained the required hardware for the configuration. For more information, see Avaya Operational Analyst Release 7.3.x Installation Planning and Prerequisites. Verify the installation of the operating system and any needed service packs or option packs. Ensure that you install Internet Information Services (IIS) while installing Microsoft Windows Server 2008 R2 (Standard and Enterprise edition) or Microsoft Windows Server 2012 Standard edition. For more information, see Avaya Operational Analyst Release 7.3.x Installation Planning and Prerequisites. Verify the installation of the supporting software on each server. For more information, see Avaya Operational Analyst Release 7.3.x Installation Planning and Prerequisites. Plan where the components resides. You require this information during installation. Plan to install Avaya OA on a disk drive separate from the physical drive on which your operating system or the database software resides. Avaya recommends this plan to improve performance. While you can install one or more Avaya OA components on a particular server, you cannot split a specific component among multiple servers. For more information, see Avaya Operational Analyst Release 7.3.x Installation Planning and Prerequisites. If you are using Oracle, decide whether to use DBA functions to establish and maintain the database instance. For more information, see Avaya Operational Analyst Release 7.3.x Installation Planning and Prerequisites. Installation and Configuration February

26 Chapter 2: Preparing for installation Verify that the minimum amount of recommended free disk space and free memory is available. Avaya support personnel have sizing tools to determine engineering specifications for specific Avaya OA systems. You can determine your free disk space, memory, and configuration specifications in collaboration with Avaya personnel. For more information, see Avaya Operational Analyst Release 7.3.x Installation Planning and Prerequisites. Verify the installation of the database. For more information, see: Avaya Interaction Center Release 7.3.x Installation Planning and Prerequisites Avaya Operational Analyst Release 7.3.x Installation Planning and Prerequisites Important: Procedure! Important: The database operations used with Avaya OA require the services of either a qualified database administrator or a systems integrator. Either the administrator or the integrator must have an in-depth knowledge of database fundamentals on the installed operating system. Verify that a user ID exists on the database that has read permission on the database. If one is nonexistent, create one. For more information, see Avaya Operational Analyst Release 7.3.x Installation Planning and Prerequisites. Verify the connection between the database client and the database server. For more information, see the database documentation. If you are collecting data from Avaya IC, verify installation and the configuration of the Avaya IC. For more information, see Avaya Interaction Center Release 7.3.x Installation and Configuration. Verify that each computer that is using the Report client or Administration client meets the minimum standards. For more information, see Avaya Operational Analyst Release 7.3.x Installation Planning and Prerequisites. Do not define a User Classpath other than what is created under normal software package installations. On Windows servers, set the Maximum Log Size of the Application Event Log to at least 2 MB, and decide setting the logs to automatically roll over. For more information, see Avaya Operational Analyst Release 7.3.x Maintenance and Troubleshooting. 26 Installation and Configuration February 2017

27 Preinstallation checklist Procedure If your configuration is using a coresident Web server on Windows, collect the security settings of your existing Web server that you recorded from Avaya Operational Analyst Release 7.3.x Installation Planning and Prerequisites. Collect the settings before you install the OA Report subsystem. On Windows servers, review your Internet Information Services (IIS) logging strategy to ensure you allocate enough free disk space. The allocation prevents message loss and Avaya OA performance impact. For more information, see Avaya Operational Analyst Release 7.3.x Installation Planning and Prerequisites. On Windows servers, open Control Panel > Services to determine if your server is using the Terminal Services. If the server is using Terminal Services, you must run a special command before and after you do any Avaya OA installs, additions, repairs, or upgrades. These commands are documented in the install, add, repair, and upgrade sections of this book. Avaya recommends that you do not install Avaya OA on the root file system on Solaris, Linux, and AIX servers. Verify that /export/home (Solaris and Linux) and /home (AIX) are not on the root file system disk. If these servers are on the root file system disk, install the software in a different location. Verify that a minimum of 2 GB of free temporary space is available on the following: c:drive for Windows /var/tmp for Solaris /tmp for RHEL /tmp for AIX. If this space is unavailable, the installer might not run successfully. Verify the availability of at least 2.2 GB of free space and 512 MB of RAM on the server where you install Real-time subsystem. Verify the installation of the time synchronization software and the software is operating correctly on all servers. For more information, see Avaya Operational Analyst Release 7.3.x Installation Planning and Prerequisites. Critical step. Verify that the servers are networked and communicating properly using dedicated IP addresses. DHCP might result in a different IP address each time a server restarts, resulting in networking failures. These failures can include validating or creating appropriate domain administrative accounts for Avaya IC and Avaya OA. For more information, see Avaya Operational Analyst Release 7.3.x Installation Planning and Prerequisites. Verify that you have the Avaya OA license keys by sending to icoakeyrequest@avaya.com with the SAP order number. Installation and Configuration February

28 Chapter 2: Preparing for installation Verify that the OS parameters, such as user IDs and locale settings, have been set as described in Avaya Operational Analyst Release 7.3.x Installation Planning and Prerequisites. For Windows, determine whether Active Directory Service (ADS) is being used for authorization. This affects how you set up the system during installation. If installing Avaya OA components on an Avaya IC server, stop the following before installing Avaya OA: Avaya IC ICM Service Avaya IC ORB Service IC Manager application Restart all after installing Avaya OA. If installing the OA Source-EC or Source-EC Bridge subsystems on an Avaya IC server, verify the availability of at least 100 MB of free disk space for the installation files. Before you install Avaya OA, turn off all virus scan software. SECURITY ALERT: Procedure! SECURITY ALERT: Temporarily turning off your virus scan software opens a potential risk for a virus attack. After you complete the installation, remember to turn on the virus scan software. Before you install Avaya OA: Back up your database. Close all other applications. Verify that the database services are running and automatic. With the services running you can configure the database during installation. If the services are not running then the installation stops and removes installed packages. When possible, use a 19-inch or larger monitor with a resolution of 1024x768 when installing Avaya OA. If you use a smaller screen resolution, you might have trouble seeing all data fields in the installation dialog boxes. You might have to resize the installation dialog boxes to see all data fields. Subsystem and client software installation considerations Decide the following when installing Avaya OA subsystems and the client software: You must install the Historical subsystem on a single system in the configuration. You can install the subsystem on a Windows, Solaris, or AIX system. 28 Installation and Configuration February 2017

29 Subsystem and client software installation considerations You can install the Real-time subsystem, basic Report subsystem, and the Administration client on any number of systems in any combination, as needed. Do not install the historical database on the same system as the real-time TimesTen database. You can install the basic Report subsystem on systems that also have the Web server software installed. You can install the Advanced Reporting subsystem only on a Windows system. You must install the Source-CMS data collection subsystem on a CMS server. You can only install the subsystem on a Solaris SPARC and RHEL system. You must install the Source-EC (Event Collector) data collection subsystem on the secondary Avaya IC server. You can install the subsystem on a Windows, Solaris, or AIX system. You must install the Source-EC Bridge (Event Collector Bridge) data collection subsystem on an Avaya IC system that also has Avaya Business Advocate. You can install the Source-EC Bridge on a Windows system. You must not install the Report client software on an Avaya OA or Avaya IC server system. Running reports on a server system can adversely affect the performance of the server software. If the Advanced Reporting subsystem and basic Report subsystem are installed on the same system, the databases allowed with the basic Report subsystem determine which database can be chosen. For Windows, Basic Reports support Oracle and Microsoft SQL. If the Advanced Reporting subsystem is also installed, the subsystem can only choose Oracle or Microsoft SQL. Only the Admin type and Runtime type of Oracle Client installation (32 bit) is certified for OA on both Microsoft Windows and Oracle Solaris platform. For Advanced reporting, Avaya OA uses COGNOS 7.4. COGNOS 7.4 runs only on the 32-bit Windows system and does not have a compatible version that can run on the 64-bit system. However, Avaya OA only supports Windows Server 2008 R2 and Windows Server 2012 R2. Therefore, you cannot use Advanced reporting on Windows Server 2008 R2, Windows Server 2012 R2, Solaris, or AIX. The Advanced Report sub system only functions on Microsoft Windows XP. Since, Microsoft Windows XP support is dropped in OA 7.3.3, Advanced Report sub system is no longer supported from OA onwards. Installation and Configuration February

30 Chapter 2: Preparing for installation Avaya OA installation examples This section shows examples of the OA-related software you must install on server and the client systems. You install software specific to Avaya IC during Avaya IC installation. For the following configuration: Site #1 Avaya IC Server ADU servers ORB Server Business Advocate Event Collector Bridge Subsystem Avaya OA server Event Collector Subsystem OA Real-time Subsystem ORB Server Avaya CMS Server #1 CMS Source-CMS Data Collection Avaya CMS Server #2 CMS Source-CMS Data Collection Avaya OA server OA Advanced Report Subsystem Database server Repository Avaya OA server OA Historical Subsystem OA Report Subsystem Administrator Desktop Web Browser OA Administration Client Avaya OA server Event Collector Subsystem OA Real-time Subsystem ORB Server Install the following OA-related software: Site #2 Avaya IC Server ADU servers ORB Server Reporting Desktop Web Browser OA Report Client At IC Site #1: - Install the Source-EC subsystem and the Real-time subsystem on the Avaya OA server. - Install the Source-EC Bridge subsystem on the Avaya IC server that has Business Advocate. On the database server, ensure the customer has already installed the database software. On the main Avaya OA server, install the Historical subsystem, Report subsystem, and Advanced Reporting subsystem. At IC Site #2, install the Source-EC subsystem and the Real-time subsystem on the Avaya OA server. On the computer the administrator uses, install the Administration client software. On the computers the supervisors uses to view reports, install the Report client software. 30 Installation and Configuration February 2017

31 Avaya OA installation examples For the following configuration: Avaya CMS Server #1 Avaya CMS Server #2 CMS Source-CMS Data Collection CMS Source-CMS Data Collection Database server Repository Avaya OA server OA Historical Subsystem OA Report Subsystem Administrator Desktop Web Browser OA Administration Client Reporting Desktop Web Browser OA Report Client Install the following OA-related software: At Avaya CMS server #1, install the Source-CMS subsystem. At Avaya CMS server #2, install the Source-CMS subsystem. On the database server, ensure the customer has already installed the database software. On the Avaya OA server, ensure you install the Historical subsystem and Report subsystem. On the computer the administrator uses, install the Administration client software. On the computers the supervisors uses to view reports, install the Report client software. Installation and Configuration February

32 Chapter 2: Preparing for installation 32 Installation and Configuration February 2017

33 Chapter 3: Installing Avaya OA components This section describes how to install the various subsystems, client software, data collection, and the Data API Utility of Avaya OA. For example, you might install some subsystems on one server, client software on other systems, and the data collection on Avaya IC and Avaya CMS servers. Avaya OA 7.3.x is a fresh install and does not support upgrading from earlier versions of Avaya OA. However, you can migrate historical data from 7.1 to 7.3.x. For more information, see Avaya Interaction Center and Operational Analyst Release 7.3.x Upgrade and Migration Guide. This section includes the following topics: Security for Unix platforms on page 33 Security for Windows platforms on page 34 Before you begin the installation on page 35 Installing Avaya OA components on a Windows platform on page 35 Installing Avaya OA components on a Solaris SPARC platform on page 63 Installing Avaya OA components on an AIX platform on page 92 Installing Avaya OA components on a CMS server - Solaris SPARC on page 117 Installing Avaya OA components on a CMS server for RHEL on page 132 Installing and testing the Report client on page 153 Completing the installation on page 160 Security for Unix platforms Avaya recommends that users avoid running Avaya software as the root user for security reasons. This does not apply to the installation software itself, which you must run as the root user. Installation and Configuration February

34 Chapter 3: Installing Avaya OA components Security for Windows platforms Avaya recommends that users avoid running Avaya software as the administrator user for security reasons. This does not apply to the installation software itself, which you must run as an administrator user. Installation checklist To install Avaya OA, perform the procedures shown in the following order: Procedure Ensure you do all prerequisites detailed in Avaya Operational Analyst Release 7.3.x Installation Planning and Prerequisites and in Preparing for installation on page 15. Read the information in Before you begin the installation on page 35 Install the Avaya OA components using the procedures in the following sections: Installing Avaya OA components on a Windows platform on page 35 Installing Avaya OA components on a Solaris SPARC platform on page 63 Installing Avaya OA components on an AIX platform on page 92 Installing Avaya OA components on a CMS server for RHEL on page 132 Install the Source-CMS subsystem on your CMS servers using the procedure in: Installing Avaya OA components on a CMS server - Solaris SPARC on page 117 Installing Avaya OA components on a CMS server for RHEL on page 132 Install the Report client files using the procedures in Installing and testing the Report client on page 153. Finish up the installation using the procedures in Completing the installation on page Installation and Configuration February 2017

35 Before you begin the installation Before you begin the installation Decide the following while you are doing the installation: Avaya recommends that you write down all user IDs and the database names used during installation. You need the information during configuration and when you make future changes. After installation, you can find most of this information using the oalist command. After installing the Administration client, you can customize the Administration client installation. For more information, see Customizing the Administration client on page 169. The dialog boxes that displays during installation depend on what components you install. Create an IC database user for Microsoft Windows SQL site, before installing Avaya OA. For example, a user called Repository that has access to the IC database. Contact the DBA for creating an IC database user. Installing Avaya OA components on a Windows platform This section describes how to install the following Avaya OA components on a Windows platform: Historical subsystem Real-time subsystem Source-EC subsystem Source-EC Bridge subsystem Report subsystem (basic) Data API Utility Advanced Reporting subsystem Administration client You can run the install from files copied to the server using FTP. For Windows, you must copy the WinSetup.exe and setup.jar files to a temporary folder. Copy these files to a disk drive that is local to the server, not a networked drive. To start the Avaya OA installation process perform the following: 1. Ensure that you have completed the prerequisites detailed in Preparing for installation on page Log in as a user with administration privileges. Installation and Configuration February

36 Chapter 3: Installing Avaya OA components CAUTION: 3. If you install Windows Terminal Services in Application mode, open a command prompt window and enter: change user /install! CAUTION: If you install Windows Terminal Services in Administration mode, you cannot properly install any Avaya OA subsystem on that system. For more information, see Avaya Operational Analyst Release 7.3.x Installation Planning and Prerequisites. 4. Put the Avaya OA DVD in the drive. 5. Using Windows Explorer, navigate to the DVD drive and double-click the WinSetup.exe file. Important: Important:! Important: Install Avaya OA from a DVD drive that is local to the server where you are installing Avaya OA. Installing from a networked DVD drive is not supported. After several seconds, the system displays the Initializing wizard window followed by the Welcome dialog box.! Important: You can stop the installation any time by clicking Cancel before you start the actual installation of files. If you click Cancel, the system displays a message to confirm your intention to cancel. If you cancel, the installation stops and the system restores to its previous state. 6. Click Next. The system displays the License Key dialog box. 36 Installation and Configuration February 2017

37 Installing Avaya OA components on a Windows platform 7. Enter the license key provided for the components purchased. 8. Click Next. The system displays the License Agreement dialog box. 9. Select the I accept the terms in the license agreement option. 10. Click Next. The system displays the User Information dialog box. Installation and Configuration February

38 Chapter 3: Installing Avaya OA components 11. Enter the User ID, User Password, Group ID, and Domain. Use a login ID, for example, oauser or biadmin and password as discussed in Avaya Operational Analyst Release 7.3.x Installation Planning and Prerequisites. This assigns an owner for all Avaya OA files and folders. If the user ID is in a domain, enter the domain name in the Domain field. If the user ID is local to this server, enter the server name in the Domain field. For the Domain field, you usually do not enter the fully qualified domain name. However, some customer networks might require use of a fully qualified domain name. Consult with the customer network administrator when configuring this option. 12. Click Next. The system displays the Destination dialog box. Important: 13. Accept the default installation folder or you can change the folder.! Important: Install the Advanced Reporting subsystem in the c:\program Files\Avaya folder for 32-bit system and the c:\program Files (X86)\Avaya folder for 64-bit system. If you intend to install Avaya OA at a location other than the c: drive, your Avaya planning and installation support representative or your Avaya Business Partner must do the custom procedure. You can install Advanced Reporting only on the Windows XP system. For more information, see Appendix B: Changing the Cognos installation on page To change the location where you intend to install the components: a. Click Browse. 38 Installation and Configuration February 2017

39 Installing Avaya OA components on a Windows platform b. Select the folder. The selected folder must be a local disk and have enough free disk space to accommodate the installed components. 15. Click Next. Specify the location where you installed Avaya IC. Based on the installed location, Avaya OA installer recognizes that Avaya IC is on the system. If you do not specify the value in this field, Avaya OA installer cannot install Event Collector (EC) and Event Collector Bridge (ECB) subsystems on the system. 16. Click Next. Installation and Configuration February

40 Chapter 3: Installing Avaya OA components There might be a long delay before the system displays the next dialog box. For performance reasons, the installer validates the destination to ensure that the installation location is on a fixed local disk. The system displays the Feature Selection dialog box. On the Feature Selection dialog box, you can see different components depending on the system on which you are installing Avaya OA. 17. Select the check box corresponding to the component that you want to install. You can install a particular component or multiple components in a combination. Important:! Important: After selecting or clearing a check box, the dialog box can take some time in seconds to refresh, and display the check mark or clear the check mark. Do not select or clear another check box until the dialog box refreshes and you can see that the check box is selected or cleared. 40 Installation and Configuration February 2017

41 Installing Avaya OA components on a Windows platform 18. Click Next. The system displays the ADS Configuration dialog box. 19. Enter the values in the fields as explained in the following table: Field Description ADS Version Enter the LDAP version being used on the authentication server. Avaya OA supports versions 2 and 3, with the default set to 3. ADS Port Enter the port number used for ADS. Avaya OA defaults to 389, which is the default when ADS is installed. OA Administration Group Distinguished Name (DN) Enter the DN for the administration group. For typical example of ADS setup, if you use the default group named oaadmin, a domain named oalab, and the company name is Telco, you enter: CN=oaadmin,CN=Users,DC=oalab,DC=telco,DC=com If you are not using ADS, use the following format for the DN: localhost\oaadmin. Installation and Configuration February

42 Chapter 3: Installing Avaya OA components Field OA Report Group Distinguished Name (DN) OA Report Writer Group Distinguished Name (DN) Description Enter the DN for the report group. For typical example of ADS setup, if you use the default group named oarpt, a domain named oalab, and the company name is Telco, you enter: CN=oarpt,CN=Users,DC=oalab,DC=telco,DC=com If you are not using ADS, use the following format for the DN: localhost\oarpt. Enter the DN for the report writer group. For typical example of ADS setup, if you use the default group named oawriter, a domain named oalab, and the company name is Telco, you enter: CN=oawriter,CN=Users,DC=oalab,DC=telco,DC=com If you are not using ADS, use the following format for the DN: localhost\oawriter. 20. Click Next. The system displays the Historical Server Configuration dialog box. The fields that appear on the Historical Server Configuration dialog box vary depending on your component selections made previously. For example, if you are installing the Advanced Reporting subsystem, but not the Report subsystem, any you can use one of the three databases, Oracle, Microsoft SQL, and DB2. If you are installing the Report subsystem, you can use only two of the three database. 42 Installation and Configuration February 2017

43 Installing Avaya OA components on a Windows platform 21. Enter the values in the fields as explained in the following table: Field Historical Subsystem Server Name Historical Database Server Name Please choose a Historical Database Create Historical Tables for these Collection Sources Alarm Services Do one of the following: Description If you are installing the Historical subsystem, the system displays the name of this server and you cannot change it. If you are not installing the Historical subsystem, enter the fully qualified domain name of the system where you install the Historical subsystem. Do one of the following: If the Historical database is on the same system where you install the Historical subsystem, enter the system name. If the historical database is on a different system than the Historical subsystem, enter the fully qualified domain name for the system where you install the Historical database. You must manually create the filegroups or tablespaces on the Historical database server before this installation can continue. For more information, see Avaya Operational Analyst Release 7.3.x Installation Planning and Prerequisites. Select the appropriate database. If the system can identify the database type based on the Historical Database Server Name, it is the only type listed. Select the collection sources for the historical tables. You can collect data from Avaya IC, CMS, or both depending on what your product license allows. If you are using a backend database, you must create filegroups or tablespaces for Avaya IC, CMS or both before selecting collection sources. For more information, see Avaya Operational Analyst Release 7.3.x Installation Planning and Prerequisites. To send alarm data to the Avaya IC server, click the IC box under Alarm Services. Then enter the fully qualified domain name of the server where you install the Source-EC subsystem in the Server Name field. Installation and Configuration February

44 Chapter 3: Installing Avaya OA components 22. Click Next. If you are installing the Historical or Report subsystems, the system displays the Database Configuration dialog box. If you are not installing the Historical or Report subsystems, continue with Step 40. The installer displays the following screen during installation of OA Release 7.3, 7.3.1, and The installer displays the following screen during installation of OA Release Installation and Configuration February 2017

45 Installing Avaya OA components on a Windows platform Important:! Important: If you are installing the Historical subsystem on a server that is separate from the Historical database, you must first install the database client software on the server where you install the Historical subsystem. Database client software is mandatory for Historical subsystem for coresident/distributed setups. 23. Use the following information to complete the dialog box. Use the values from your database installation, which is described in Avaya Operational Analyst Release 7.3.x Installation Planning and Prerequisites. Some of the fields might include default values. Field Oracle Microsoft SQL DB Administrator ID DB Administrator Password OA DB User ID OA DB User Password Valid Oracle user. This user might be the default user system or any user with DBA privileges. Password for the DB Administrator ID. User ID for the Avaya OA database (Avaya OA creates this user ID during a new installation). User password for the Avaya OA database. Valid SQL user. This user might be the default user sa or any user with DBA privileges. Password for the DB Administrator ID. User ID for the Avaya OA database (Avaya OA creates this User ID during a new installation). User password for the Avaya OA database. Installation and Configuration February

46 Chapter 3: Installing Avaya OA components OA Database Name NA. New database name that is created during install, for example, oadb. IC DB User ID 1 IC DB User Password 1 User ID for the Avaya IC Repository database (this must be an existing Avaya IC user ID, for example, repository). User password for the Avaya IC Repository user ID. User ID for the Avaya IC Repository database (this must be an existing Avaya IC user ID, for example, repository). User password for the Avaya IC Repository user ID. IC Repository Database 1 NA. Avaya IC Repository database name (for example, repository). DB Instance Name TCP/IP Port Number Field Oracle Microsoft SQL Oracle TNS Server Name Avaya IC and Avaya OA database instance name (if using the default configuration, otherwise the port number specified during database installation). A valid TNS server name. This name is assigned by the database administrator during Oracle installation. The default name is dbservername.oadb. You must check the tnsnames.ora file and use the exact entry found there. If an entry is not found, ask the DBA to create a tnsnames.ora entry and then use the exact entry found there. Avaya IC and Avaya OA database instance name (MSSQLSERVER if you used the default database instance) (if using the default configuration, otherwise the port number specified during database installation). N/A 46 Installation and Configuration February 2017

47 Installing Avaya OA components on a Windows platform Field Oracle Microsoft SQL SQL Server DataBase Name N/A New Microsoft SQL database created during installation. Oracle_Home (Client) This filed refers to the Oracle DB client home location. This field is applicable on OA Release N/A Ensure that the tnsnames.ora file exists on the server where OA Historical is being installed. This file is found in the following location: ORACLE_HOME /network/ admin of the Oracle Client installation. If this file does not exist, then you will need to create it. Ensure that the Oracle Client Home selected is of the compatible version that OA would use to connect to the appropriate DB Server. Refer to the Oracle documentation to check on the compatibility matrix for client/server connectivity. On Windows server where OA historical subsystem is installed, ensure that Windows environmental path variable (PATH) has the path of the Oracle Home (Client). 1. This field does not display if you do not use Avaya IC as a collection source. During the creation of the Repository Database using Oracle as your database software, you are to provide a password for the Repository database. Use this name as your IC DB User ID along with the password you enter. 24. Click Next. The system displays a warning message about the Oracle archive log. One of the following occurs: For Oracle, continue with the next step. For Microsoft SQL, continue with Step 27. Installation and Configuration February

48 Chapter 3: Installing Avaya OA components 25. Click OK to accept the warning, if displayed. For Oracle, the system scans the TNSnames.ora file to determine if the TNS server name is within that file. If the TNSnames.ora file contains the TNS server name, the installer continues with Step 29. However, if the TNSnames.ora file does not contain TNS server name, the system displays the following warning message asking if you want the installer to change the TNSnames.ora file to include the TNS server name. 26. Click Yes. The installer tries to edit the TNSnames.ora file. One of the following occurs: - If the permissions on the TNSnames.ora file allow writing, the installer modifies the TNSnames.ora file to include the administered TNS server name and the installation continues. - If the permissions on the TNSnames.ora file are read-only, the installer cannot change the TNSnames.ora file. The system displays a message stating that you must change the permissions on the TNSnames.ora file. Click OK to return to the Database Configuration dialog box. You must change permissions on the file to continue with the install. If you click No, the system displays the Database Configuration dialog box. The system does not go further until you add the TNS server name in the TNSnames.ora file. 48 Installation and Configuration February 2017

49 Installing Avaya OA components on a Windows platform There might be a long delay before the system displays the next dialog box. If you are using the Microsoft SQL database and if the database is coresident with Historical subsystem, the system displays the SQL Database Options dialog box. Enter the values in the fields or click Next. 27. Select Use Existing DB to use an existing database. 28. Enter the location and size of the Microsoft SQL Server Transaction Log. You can use the default location and size. 29. Click Next. If you are installing the Historical subsystem, the system displays the OA Common TableSpaces dialog box. Installation and Configuration February

50 Chapter 3: Installing Avaya OA components Important:! Important: If the database is on a back-end database server, the system does not display any table space dialog boxes. Continue with the Step Enter the correct location and size for each common filegroup or tablespace. For more information, see Avaya Operational Analyst Release 7.3.x Installation Planning and Prerequisites. If the filegroups and tablespaces do not already exist, the Use Existing checkboxes does not display and the Location and Size input fields include default values you can edit. If the filegroups and tablespaces do already exist, the Use Existing checkboxes are selected. You can clear the check boxes and enter a different location and size. 50 Installation and Configuration February 2017

51 Installing Avaya OA components on a Windows platform 31. Click Next. If the system collects the data from CMS, the system displays the OA CMS Specific dialog box. 32. Enter the correct location and size for each filegroup or tablespace. For more information, see Avaya Operational Analyst Release 7.3.x Installation Planning and Prerequisites. If the filegroups and tablespaces do not already exist, the Use Existing checkboxes does not display and the Location and Size input fields include default values you can edit. If the filegroups and tablespaces do already exist, the Use Existing checkboxes are selected. You can clear the checkboxes and enter a different location and size. 33. Click Next. If you are not installing the Real-time subsystem, but you selected CMS and did not select IC on the Historical Server Configuration dialog box, and either: The environment variable BI_DONT_RUN_DBSETUP is undefined, or Installation and Configuration February

52 Chapter 3: Installing Avaya OA components The variable value is not set to "true" the system displays the Historical Database Locale dialog box. 34. Select the appropriate locale for your installation. 35. Click Next. If the system collects data from Avaya IC, the system displays the OA IC Specific dialog box. 36. Enter the correct location and size for each filegroup or tablespace. For more information, see Avaya Operational Analyst Release 7.3.x Installation Planning and Prerequisites. 52 Installation and Configuration February 2017

53 Installing Avaya OA components on a Windows platform If the filegroups and tablespaces do not already exist, the Use Existing checkboxes does not display and the Location and Size input fields include default values you can edit. If the filegroups and tablespaces do already exist, the Use Existing checkboxes are selected. You can clear the check boxes and enter a different location and size. 37. Click Next. The system displays a warning dialog box about storing of historical data on a disk. 38. Click OK to accept the warning, if displayed. If you are not installing the Real-time subsystem, but you selected IC on the Historical Server Configuration dialog box, and either: The environment variable BI_DONT_RUN_DBSETUP is undefined, or The variable value is not set to "true" the system displays the Historical Database Locale dialog box. 39. Select the appropriate locale for your installation. Installation and Configuration February

54 Chapter 3: Installing Avaya OA components 40. Click Next. If you are installing the Real-time subsystem, the system displays the Real-time Configuration dialog box. However, if you are not installing the Real-time subsystem, continue with the Step In the Real Time DB Location field, enter a path that is on a different disk drive from where you install the Avaya OA software is, and that has at least 2.2 GB of free disk space. 42. Click the Real Time DB Size (M) field and select Click Next. Important:! Important: If you do not have at least 2.2 GB of free disk space to install TimesTen, the system displays a warning message. You cannot continue until you have at least 2.2 GB of disk space available. If you are not installing the Real-time subsystem, but you selected IC on the Historical Server Configuration dialog box, and either: The environment variable BI_DONT_RUN_DBSETUP is undefined, or 54 Installation and Configuration February 2017

55 Installing Avaya OA components on a Windows platform The variable value is not set to "true" the displays the Historical Database Locale dialog box. 44. Select the appropriate locale for your installation. 45. Click Next. If you are installing the Administration client, the system displays the Administration client locale settings dialog box. If you are not installing the Administration client, continue with the Step Click the Historical Database Locale field and select a locale setting. Installation and Configuration February

56 Chapter 3: Installing Avaya OA components 47. Click Next. The system displays the Installation Preview dialog box and lists the components you have selected. 48. Scroll through the preview dialog box to verify the selected components and the configuration data. 56 Installation and Configuration February 2017

57 Installing Avaya OA components on a Windows platform CAUTION:! CAUTION: Do not close the Progress dialog box after you have clicked Next in the following step. If you close the Progress dialog box after the installation has started, you disrupt the installation. Then you must contact Avaya support to do a manual cleanup of the installation. 49. Click Next to run the installation. The system displays the Progress dialog box showing the installation progress. The installation can take several minutes. Near the end of the installation, the dialog box can go blank for some time. When the installation is complete, the system displays the Install Complete dialog box. Installation and Configuration February

58 Chapter 3: Installing Avaya OA components Important: 50. Select the Yes, restart my computer option and then click Next. The system displays the Restart System dialog box. 51. Select the option to restart your system now and click Next.! Important: You must always restart a Windows server at this time for Avaya OA to operate properly. If you are not requested to restart the server, you must manually restart the server. 52. Remove the Avaya OA DVD and store it in a safe location. Verifying the Avaya OA installation on Windows platform 1. Log in to the system using an Avaya OA user ID and password. For more information, see Avaya Operational Analyst Release 7.3.x Installation Planning and Prerequisites. 2. Open a command prompt window. 3. If Terminal Services is enabled, enter: change user /execute 4. In the command prompt window, enter the following command to show what processes are running: pa list The system displays a list similar to the following.. system boot Jan 20 13:10. run-level 4 Jan 20 13:10 4 java. Jan : id=admb java. Jan : id=adm0 java. Jan : id=ams java. Jan : id=aut java. Jan : id=schd There should be several Java entries, and these lines should not have an exit code at the end of the line. If there are any exit codes displayed on the Java entries and that process is not running, escalate the problem to Avaya Technical Support. The id=aut and id=schd are displayed only when you install the Historical subsystem. 58 Installation and Configuration February 2017

59 Installing Avaya OA components on a Windows platform The recorder entries are displayed only if you are collecting data from CMS or Avaya IC. Forwarder entries might be displayed on a server that has the Real-time subsystem installed. 5. If you get the message mom is not active, enter: pa start all 6. Repeat Step 4 to verify that Avaya OA has started. Installation and Configuration February

60 Chapter 3: Installing Avaya OA components 7. Enter: oalist The system displays a message similar to the following, which lists what components you installed on this system: Subsystems installed Historical Real Time Reports Data API Utility Source-EC Advanced Reports Administration Client Server Names Historical: punoasvorsr03 Historical Database: <IP_Address_of_Historical_Database_System> Database information Type: MSSQL AdminID: sa UserID: oadba Instance Name: MSSQLSERVER Port Number: 1433 OA DB Name: oadb IC UserID: repository IC Repository DB Name: repository Using a Backend/Remote Database IC Historical Tables created User information OA User ID: biadmin Domain: punoadom Group ID: oaadmin Active Directory Server or Localhost Information ADS Version: 3 ADS Port: 389 ADS Admin Group: CN=oaadmin,OU=OA Admins,DC=punoadom,DC=avaya,DC=com ADS Report Group: CN=oarpt,OU=OA Admins,DC=punoadom,DC=avaya,DC=com ADS Report Writer Group: CN=oawriter,OU=OA Admins,DC=punoadom,DC=avaya,DC=com Admin Client Locale Admin Client Locale: en_us OA Software information Version Installed: From the Windows Start menu, select Programs > Administrative Tools > Services. 9. Validate that the following services are running and you set the services run automatically. If you have installed the Historical subsystem, check for the following: 60 Installation and Configuration February 2017

61 Configuring OA Administration client on Microsoft Windows 10 - Avaya Business Intelligence Service - ORBacus Naming Service If you have installed the Real-time subsystem, check for the following: - Avaya Business Intelligence Service - ORBacus Naming Service - TimesTen Data Manager If you have installed the Report subsystem, check for the following: - Avaya Business Intelligence service - ORBacus Naming Service - Tomcat service. - For OA and earlier the service name is Stumbras-Tomcat. - For OA and later the service name is Avaya OA Reporting Application. If you have installed the Source-EC subsystem, check for the following: - ORBacus Naming Service Configure the above properties to run automatically, if the above properties are not configured to run automatically. 10. If you are not successful starting Avaya OA, see Avaya Operational Analyst Release 7.3.x Maintenance and Troubleshooting Guide for more troubleshooting information. Configuring OA Administration client on Microsoft Windows 10 Microsoft Edge browser is the default browser for Microsoft Windows 10 operating system. By default after installing Avaya OA Administration client, the desktop icon which launches the OA Administration client opens in the Edge browser. Avaya OA application does not support Microsoft Edge browser. To use Avaya OA Administration client on Microsoft Windows 10, you must modify the files of type (.html) to open in Microsoft Internet Explorer 11 (32-bit) browser only. Perform the following procedure on the Microsoft Windows 10 system where OA Administration client is installed to change the default program for launching the.html files. 1. Click Start > Control Panel > Default Programs > Set your default programs. 2. In the left pane select Internet Explorer. 3. Click the Choose defaults for this program option and select.html file. Installation and Configuration February

62 Chapter 3: Installing Avaya OA components 4. Click Save. 5. Double clicking the Avaya OA Administration client on the desktop to launch the client in Internet Explorer browser. On Windows 10 desktop after logging in as an administrator user, if you double click the Administration client desktop icon and the Administration client does not launch successfully. This may happen due to Windows 10 enhanced security. To resolve this issue, you can: Change local Security policies of the Windows 10 system. Launch the Internet Explorer browser in the administrator mode. Changing Local Security Policy 1. As a user with Administrative rigths, click Start > Run. 2. In the Run window type secpol.msc and press Enter. 3. Goto Security Settings > Local Policies > Security options and set the values of the following variables as follows: Policy User Account Control: Admin Approval Mode for the Built-in Administrator account User Account Control: Behaviour of the elevation prompt for administrators in Admin Approval Mode User Account Control: Run all administrators in Admin Approval Mode Value Disabled Elevate without prompting Disabled 4. Restart the Microsoft Windows 10 system for the changes to take effect. Launching Microsoft Internet Explorer in Administrator mode 1. Goto C:\Program Files (x86)\internet Explorer folder. 2. Right-click iexplorer.exe and click Run as administrator. 3. In the Internet Explorer browser press Alt+F > File > Open. 4. In the Open window open %PABASE%/AdminPol.html to launch the OA Administration client. 62 Installation and Configuration February 2017

63 Installing Avaya OA components on a Solaris SPARC platform During OA Administration client launch, the browser would display JRE upgrade dialog box. You must not upgrade the JRE. Installing Avaya OA components on a Solaris SPARC platform This section describes how to install the following Avaya OA components on a Solaris platform: Historical subsystem Real-time subsystem Source-EC subsystem Report subsystem (basic) Data API Utility For more information, see Installing Avaya OA components on a CMS server - Solaris SPARC on page 117. The dialog boxes shown in this section are based on using the CDE interface. If the customer is using the OpenWin interface, the installation dialog boxes appear different. Avaya recommends that you use the CDE interface for installation. You can run the install from files copied to the server using FTP. For Solaris, you must copy the SolSetup and setup.jar files to a temporary folder on a disk drive that is local to the server, not a networked drive. You must also reset the permissions on Solsetup using the chmod +x SolSetup command. To run the Avaya OA installation process on Solaris platforms perform the following: 1. Ensure you have completed the prerequisites detailed in Preparing for installation on page Log in as root. 3. Put the Avaya OA DVD in the drive and wait about 15 seconds. Installation and Configuration February

64 Chapter 3: Installing Avaya OA components Important:! Important: Install Avaya OA from a DVD drive that is local to the server where you are installing Avaya OA. Installing from a networked DVD drive is not supported. A file manager window might display showing the contents of the DVD. Minimize this window. If the File Manager window does not open, enter the following commands to run the volume manager: /etc/init.d/volmgt stop /etc/init.d/volmgt start 4. If you are installing the Historical subsystem with a backend database, and installing the Oracle 10g Client on this system, run the following command to set the Oracle environment:. $ORACLE_HOME/.profile If you fail to run this command, the system displays this error: Cannot find the Oracle instance id $dbsid from Oracle init file or from environment. Ensure you correctly install Oracle and for Oracle 10g, ensure to run.profile.login before running install. 64 Installation and Configuration February 2017

65 Installing Avaya OA components on a Solaris SPARC platform 5. From a terminal window, enter the following commands: cd /cdrom/cdrom0./solsetup After several seconds, the system displays the Initializing wizard window followed by the Welcome dialog box. Important:! Important: You can stop the installation any time by clicking Cancel before you run the actual installation of files (see Step 44). If you click Cancel, you are asked to confirm your intention to cancel. If you cancel, installation terminates and the system restores to the previous state. Installation and Configuration February

66 Chapter 3: Installing Avaya OA components 6. Click Next. The system displays the License Key dialog box. 7. Enter the provided license key for the purchased components and click Next. The system displays the License Agreement dialog box. 66 Installation and Configuration February 2017

67 Installing Avaya OA components on a Solaris SPARC platform 8. Select the I accept the terms in the license agreement option and then click Next. The system displays the User Information dialog box. 9. Enter the User ID, User Password, and Group ID. Use a login ID, for example, oauser or biadmin, and password as discussed in Avaya Operational Analyst Release 7.3.x Installation Planning and Prerequisites. This assigns an owner for all OA files and folders. Important:! Important: The group ID must be the primary group ID for the user ID. Installation and Configuration February

68 Chapter 3: Installing Avaya OA components 10. Click Next. The system displays the Destination dialog box. Important: In the Destination dialog box, specify the installation location of the Avaya OA software. The default installation location is the folder defined for the user ID.! Important: Avaya recommends that you do not install Avaya OA on the root file system on Solaris servers. Verify that /export/home is not on the root file system disk. If it is on the root file system disk, install the software in a different location. 11. Accept the default folder or change the folder, if needed. If you are using an NIS user ID not local to the server, the destination field displays a "/" in the field. You must change this and provide the valid path. 12. To change the location where you want the components installed perform the following: a. Click Browse. b. Select the folder. The selected folder must have enough free disk space to accommodate the installed components. The folder must be on a local disk and not a remote file system. You cannot install Avaya OA software in any of the following system folders: / (the root directory) /etc /var /tmp 68 Installation and Configuration February 2017

69 Installing Avaya OA components on a Solaris SPARC platform /usr/lib /opt/bi 13. Click Next. The system displays the Avaya IC Install Location dialog box. Specify the location where you installed Avaya IC. Based on the specified location, the Avaya OA installer recognizes that Avaya IC is installed on the system. If you keep this field empty, the Avaya OA installer cannot install EC and ECB subsystems on the system. 14. Click Next. Installation and Configuration February

70 Chapter 3: Installing Avaya OA components There might be a long delay before the system displays the next dialog box. The system displays the Feature Selection dialog box. Important: 15. Select the check box corresponding to the component that you want to install. You can install each component or multiple components in a combination.! Important: After selecting or clearing a check box, there can be a delay of few seconds before the system refreshes the dialog box and you see the check mark or the check mark is cleared. Do not select or clear another check box until the dialog box refreshes and you can see that the check box is selected or cleared. 16. Click Next. One of the following occurs: If you are not installing the Historical subsystem or Report subsystem, continue with the Historical Server configuration (Step 20). 70 Installation and Configuration February 2017

71 Installing Avaya OA components on a Solaris SPARC platform If you are installing the Historical subsystem or the Report subsystem, the system displays the Reports Configuration dialog box. The dialog box displays the Reports Group ID option and Report Writer Group ID option only when you are installing the Historical subsystem. The system displays the other options only when you are installing the Report subsystem. 17. Enter the following information: Reports Group ID Field Report Writer Group ID Description oarpt This is the recommended ID and must match the group ID administered in Avaya Operational Analyst Release 7.3.x Installation Planning and Prerequisites. oawriter This is the recommended ID and must match the group ID administered in Avaya Operational Analyst Release 7.3.x Installation Planning and Prerequisites. Installation and Configuration February

72 Chapter 3: Installing Avaya OA components 18. Click Next. The system displays the Historical Server Configuration dialog box. The fields that the dialog box displays can vary depending on the components that you selected in the earlier steps. 19. Enter the field values as explained in the following table: Field Historical Subsystem Server Name Historical Database Server Name Do one of the following: Description If you are installing the Historical subsystem, the system displays the name of this server and you cannot change the sever name. If you are not installing the Historical subsystem, enter the fully-qualified domain name of the system where you installed the Historical subsystem. Do one of the following: If the Historical database is on the same system where you install the Historical subsystem is, enter the system name. If the Historical database is on a different system than where you install the Historical subsystem is, enter the fully qualified domain name for the system where you install the Historical database is. You must manually create the filegroups or tablespaces on the Historical database server before this installation can continue. For more information, see Avaya Operational Analyst Release 7.3.x Installation Planning and Prerequisites. 72 Installation and Configuration February 2017

73 Installing Avaya OA components on a Solaris SPARC platform Field Please choose a Historical Database Create Historical Tables for these Collection Sources Alarm Services Description Select the appropriate database. If the system can identify the database type based on the Historical Database Server Name, it is the only type listed. Select the collection sources for the historical tables. You can collect data from Avaya IC, CMS, or both depending on what your product license allows. If you are using a backend database, you must create filegroups or tablespaces for Avaya IC, CMS or both before selecting collection sources. For more information, see Avaya Operational Analyst Release 7.3.x Installation Planning and Prerequisites. To send alarm data to the Avaya IC server, click the IC box under Alarm Services. Then enter the fully qualified domain name of the server where you install the Source-EC subsystem is in the Server Name field. For an Avaya OA and CMS configuration without Avaya IC, leave these options blank. Installation and Configuration February

74 Chapter 3: Installing Avaya OA components 20. Click Next. If you are installing the Historical or Report subsystems, the system displays the Database Configuration dialog box. The installer displays the following screen during installation of OA Release 7.3, 7.3.1, and The installer displays the following screen during installation of OA Release Installation and Configuration February 2017

75 Installing Avaya OA components on a Solaris SPARC platform 21. Use the following information to complete the dialog box. Important:! Important: If you are installing the Historical subsystem on a server that is separate from the Historical database, you must first install the database client software on the server where you installed the Historical subsystem. The database client software is mandatory for Historical subsystem for coresident/distributed setups. Field DB Administrator ID DB Administrator Password OA DB User ID OA DB User Password OA Database Name Value Valid Oracle user. This ID might be the default user system or any user with DBA privileges. Password for the DB Administrator ID User ID for the Avaya OA database (Avaya OA creates this user ID during a new installation) User password for the Avaya OA database New database name that is created during install, for example, oadb. Installation and Configuration February

76 Chapter 3: Installing Avaya OA components Field IC DB User ID 1 IC DB User Password 1 IC Repository Database 1 DB Instance Name TCP/IP Port Number Oracle TNS Server Name Oracle_Home (Client) Value User ID for the Avaya IC Repository database. This must be an existing Avaya IC user ID, for example, repository. User password for the Avaya IC Repository user ID. Avaya IC Repository database name, for example, repository. Avaya IC and Avaya OA database instance name (if using the default configuration, otherwise the port number specified during database installation; see Avaya Operational Analyst Release 7.3.x Installation Planning and Prerequisites). A valid TNS server name. The database administrator assigns this name during Oracle installation. The default name is dbservername.oadb. You must check the tnsnames.ora file and use the exact entry you find there. If an entry is not found, ask the DBA to create a tnsnames.ora entry and then use the exact entry you find there. This filed refers to the Oracle DB client home location. This field is applicable on OA Release Ensure that the tnsnames.ora file exists on the server where OA Historical is being installed. This file is found in the following location: ORACLE_HOME / network/admin of the Oracle Client installation. If this file does not exist, then you will need to create it. When Oracle client is installed, the tnsnames.ora file does not exist. Ensure that the tnsnames.ora file is created with correct set of permissions (666) and with suitable owner/group ownership, [oracle/oinstall] Ensure that the Oracle Client Home selected is of the compatible version that OA would use to connect to the appropriate DB Server. Refer to the Oracle documentation to check on the compatibility matrix for client/server connectivity. 1. This field does not display if you do not use Avaya IC as a collection source. During the creation of the Repository Database using Oracle as your database software, you are asked to provide a password for the Repository database. Use this name as your IC DB User ID with the password you enter. 76 Installation and Configuration February 2017

77 Installing Avaya OA components on a Solaris SPARC platform 22. Click Next. The system can display a warning message about the Oracle archive log. 23. Click OK to accept the warning. The installer scans the TNSnames.ora file to determine if the TNS server name is within that file. If the TNSnames.ora file contains the TNS server name, the installer continues with the next step. If the TNSnames.ora file does not contain the TNS server name, the system displays the following warning message asking if you want the installer to change the TNSnames.ora file to include the TNS server name. 24. Click Yes. The installer tries to edit the file. One of the following occurs: - If the permissions on the TNSnames.ora file allow writing, the installer changes the TNSnames.ora file to include the administered TNS server name and the installation continues. - If the permissions on the TNSnames.ora file are read-only, the installer cannot change the TNSnames.ora file and displays a message stating to change permissions of the file. Click OK to return to the Database Configuration dialog box. You must change permissions on the file to continue with the installation. If you click No, the system displays the Database Configuration dialog box. The system does not go further until you resolve the TNS server name issue. Installation and Configuration February

78 Chapter 3: Installing Avaya OA components There might be a long delay before the system displays the next dialog box. The system displays the OA Common Table Spaces dialog box. If you are not installing the Historical subsystem or if the database is on a back-end database server, the system does not display any dialog box in this section. Continue with Step Enter the correct location and the size for each tablespace. For more information, see Avaya Operational Analyst Release 7.3.x Installation Planning and Prerequisites. If the tablespaces does not already exist, you cannot see the check boxes under the Use Existing column and the Location and Size fields includes default values you can edit. If the tablespaces already exists, you can see that the check boxes under the Use Existing column are selected. You can clear the checkboxes and enter a different location and the size in the Location and Size fields. 78 Installation and Configuration February 2017

79 Installing Avaya OA components on a Solaris SPARC platform 26. Click Next. If the system collects the data from CMS, the system displays the OA CMS Specific dialog box. 27. Enter the correct location and the size for each tablespace. For more information, see Avaya Operational Analyst Release 7.3.x Installation Planning and Prerequisites. If the tablespaces does not already exist, you cannot see the check boxes under the Use Existing column and the Location and Size fields includes default values you can edit. If the tablespaces already exists, you can see that the check boxes under the Use Existing column are selected. You can clear the checkboxes and enter a different location and the size in the Location and Size fields. 28. Click Next. If you are not installing the Real-time subsystem, but on the Historical Server Configuration dialog box (Step 18 of this procedure), you select CMS (and did not select Avaya IC), and either: The environment variable BI_DONT_RUN_DBSETUP is undefined, or Installation and Configuration February

80 Chapter 3: Installing Avaya OA components The variable value is not set to "true" The system displays the Historical Database Locale dialog box. 29. Select the appropriate locale for your installation. 30. Click Next. If the system collects the data from Avaya IC, the system displays the OA IC Specific. 31. Enter the correct location and the size for each tablespace. For more information, see Avaya Operational Analyst Release 7.3.x Installation Planning and Prerequisites. 80 Installation and Configuration February 2017

81 Installing Avaya OA components on a Solaris SPARC platform If the tablespaces does not already exist, you cannot see the check boxes under the Use Existing column and the Location and Size fields includes default values you can edit. If the tablespaces already exists, you can see that the check boxes under the Use Existing column are selected. You can clear the checkboxes and enter a different location and the size in the Location and Size fields. 32. Click Next. The system displays a warning message about storing historical data on a disk. 33. Click OK to accept the warning. 34. If you are not installing the Real-time subsystem, but you selected IC on the Historical Server Configuration dialog box (Step 18 of this procedure), and either: The environment variable BI_DONT_RUN_DBSETUP is undefined, or The variable value is not set to "true" The system displays the Historical Database Locale dialog box. 35. Select the appropriate locale for your installation. 36. Click Next. One of the following occurs: If you are not installing the Real-time subsystem, continue with Step 39. Installation and Configuration February

82 Chapter 3: Installing Avaya OA components If you are installing the Real-time subsystem, the system displays the Real-time Configuration dialog box. Important: 37. In the Real Time DB Location field, enter a path that is on a different disk drive from where you install the Avaya OA software is. Ensure that the drive has at least 2.2 GB of free disk space. 38. In the Real Time DB Size (M) field, the only option is Click Next.! Important: If you do not have at least 2.2 GB of free disk space to install TimesTen, the system displays a warning message. You cannot continue until at least 2.2 GB of disk space is available. 40. If you are not installing the Real-time subsystem, but you selected IC on the Historical Server Configuration dialog box (Step 18 of this procedure), and either: The environment variable BI_DONT_RUN_DBSETUP is undefined, or 82 Installation and Configuration February 2017

83 Installing Avaya OA components on a Solaris SPARC platform The variable value is not set to "true". The system displays the Historical Database Locale dialog box. 41. Select the appropriate locale for your installation. Installation and Configuration February

84 Chapter 3: Installing Avaya OA components 42. Click Next. The system displays the Installation Preview dialog box listing the components that you selected. 43. Scroll through the preview dialog box to verify the selected components and the configuration data. 84 Installation and Configuration February 2017

85 Installing Avaya OA components on a Solaris SPARC platform CAUTION:! CAUTION: Do not close the Progress dialog box after you have clicked Next in the following step. If you close the Progress dialog box after the installation has started then you disrupt the installation. You must contact Avaya support to do a manual cleanup of the installation. 44. Click Next to run the installation. The system displays the Progress dialog box showing the progress of the installation. The installation process can take several minutes. Near the end of the installation, the Progress dialog box can become blank for some time. After the installation is complete, the system displays the Install Complete dialog box. Installation and Configuration February

86 Chapter 3: Installing Avaya OA components 45. Click Next. The system displays the Install Successful dialog box. 46. Click Next. 47. Close all, but one terminal window and enter: cd / eject cdrom 48. Remove the Avaya OA DVD. 86 Installation and Configuration February 2017

87 Installing Avaya OA components on a Solaris SPARC platform Verifying Avaya OA installation on Solaris SPARC platform CAUTION: 1. Log out of the desktop environment. 2. Log in to the system using an Avaya OA user ID and password. For more information, see Avaya Operational Analyst Release 7.3.x Installation Planning and Prerequisites.! CAUTION: Do not use any Avaya OA commands while logged in as root. Using the root login ID on these commands changes ownership of files and makes them unusable by the Avaya OA user ID. 3. Enter:. /opt/bi/.profile 4. Enter the following command to show what processes are running: pa list The system displays a message similar to the following:. system boot Jan 20 07:54. run-level 4 Jan 20 10:23 4 java. Jan 20 07: id=admb java. Jan 20 07: id=adm0 java. Jan 20 16: id=ams java. Jan 20 07: id=aut java. Jan 20 07: id=schd There should be several Java entries, and these lines should not have an exit code at the end of the line. If there are any exit codes displayed on the Java entries that process is not running. Escalate the problem to Avaya Technical Support. The id=aut and id=schd only displays when you install the Historical subsystem. The recorder entries display only if you are collecting data from CMS or Avaya IC. Forwarder entries might display on a server that has the Real-time subsystem installed. 5. If you get the message mom is not active, enter: pa start all Installation and Configuration February

88 Chapter 3: Installing Avaya OA components 6. Repeat Step 6 to verify Avaya OA is running. If you are not successful starting Avaya OA, see Avaya Operational Analyst Release 7.3.x Maintenance and Troubleshooting Guide for more troubleshooting information. 7. Enter the following command: oalist The system displays a message similar to the following: Subsystems installed Historical Real Time Reports Data API Utility Source-EC Server Names Historical: puoadvsolsr11 Historical Database: <IP_Address_of_Historical_Database_System> Reports: puoadvsolsr11 Database information Type: ORACLE AdminID: system UserID: oadb Instance Name: orcl Port Number: 1521 IC UserID: repository Using a Backend/Remote Database IC Historical Tables created User information OA User ID: biadmin Group ID: oaadmin Reports information Reports Group ID: oarpt Report Writer Group ID: oawriter Tomcat Home: /export/home/biadmin/bi/stumbras/tomcat Tomcat Port: 9080 OA Software information Version Installed: If you have installed the Historical subsystem, use the following commands and responses to verify that the required services are running. If the services are not running, escalate the problem using the normal channels. 88 Installation and Configuration February 2017

89 Installing Avaya OA components on a Solaris SPARC platform a. Enter the following command to determine if the Avaya Business Intelligence Service is running: ps -ef grep initsrv The system displays a message similar to the following: root Jan 20? 0:06 /opt/bi/bin/initsrv -n oaadmin -v 30 biadmin :28:00 pts/11 0:00 grep initsrv b. Enter the following command to determine if the ORBacus Naming Service is running: ps -ef grep naming The system displays a message similar to the following: biadmin Jan 20? 6:48 /export/home/biadmin/ jre<version_number>/bin/java -Dooc.naming.port=10000 com.ooc.cosn biadmin :27:35 pts/3 0:00 grep naming 9. If you have installed the Real-time subsystem, use the following commands and responses to verify that the required services are running. If the services are not running, escalate the problem using the normal channels. a. Enter the following command to determine if the Avaya Business Intelligence Service is running: ps -ef grep initsrv The system displays a message similar to the following: root Jan 20? 0:06 /opt/bi/bin/initsrv -n oaadmin -v 30 biadmin :28:00 pts/11 0:00 grep initsrv b. Enter the following command to determine if the ORBacus Naming Service is running: ps -ef grep naming The system displays a message similar to the following: biadmin Jan 20? 6:48 /export/home/biadmin/ jre<version_number>/bin/java -Dooc.naming.port=10000 com.ooc.cosn biadmin :27:35 pts/3 0:00 grep naming Installation and Configuration February

90 Chapter 3: Installing Avaya OA components c. Enter the following command to determine if the TimesTen Data Manager is running: ps -ef grep timesten The system displays a message similar to the following: root Jan 20? 0:01 /export/home/biadmin/timesten5.1.34/ TimesTen/avaya_bi/bin/timestend root Jan 20? 0:00 /export/home/biadmin/timesten5.1.34/ TimesTen/avaya_bi/bin/timestensubd -id 0 root Jan 20? 0:00 /export/home/biadmin/timesten5.1.34/ TimesTen/avaya_bi/bin/timestensubd -id 1 root Jan 20? 0:00 /export/home/biadmin/timesten5.1.34/ TimesTen/avaya_bi/bin/timestensubd -id 2 root Jan 20? 0:00 /export/home/biadmin/timesten5.1.34/ TimesTen/avaya_bi/bin/timestensubd -id 3 biadmin :34:22 pts/11 0:00 grep timesten 10. If you have installed the Report subsystem, use the following commands and responses to verify that the required services are running. If the services are not running, escalate the problem using the normal channels. a. Enter the following command to determine if the Avaya Business Intelligence Service is running: ps -ef grep initsrv The system displays a message similar to the following: root Jan 20? 0:06 /opt/bi/bin/initsrv -n oaadmin -v 30 biadmin :28:00 pts/11 0:00 grep initsrv b. Enter the following command to determine if the ORBacus Naming Service is running: ps -ef grep naming The system displays a message similar to the following: biadmin Jan 20? 6:48 /export/home/biadmin/ jre<version_number>/bin/java -Dooc.naming.port=10000 com.ooc.cosn biadmin :27:35 pts/3 0:00 grep naming 11. If you have installed the Source-EC subsystem, use the following commands and responses to verify that the required services are running. If the services are not running, escalate the problem using the normal channels. 90 Installation and Configuration February 2017

91 Installing Avaya OA components on a Solaris SPARC platform a. Enter the following command to determine if the ORBacus Naming Service is running: ps -ef grep naming The system displays a message similar to the following: biadmin Jan 20? 6:48 /export/home/biadmin/ jre<version_number>/bin/java -Dooc.naming.port=10000 com.ooc.cosn biadmin :27:35 pts/3 0:00 grep naming CAUTION: 12. Start the Tomcat server after you configure the Admin client. For more information, see Administration client options on page 168. a. Log in to the Solaris system using an Avaya OA user ID and password. For more information, see Avaya Operational Analyst Release 7.3.x Installation Planning and Prerequisites.! CAUTION: Do not use any Avaya OA commands while logged in as root. Using the root login ID on these commands changes ownership of files and makes them unusable by the Avaya OA user ID. b. Enter the command:./opt/bi/.profile. c. Go to the Tomcat server location. Enter the command: cd /opt/bi/stumbras/tomcat/bin. d. Start the Tomcat server. Enter the command: For OA and earlier:./startup.sh For OA and later:./startoareport.sh 13. Check the Tomcat server logs to verify that Tomcat is running successfully. a. Go to the $PABASE/stumbras/tomcat/logs/ folder. b. Enter the command: vi catalina.out 14. Check if the Tomcat server is running successfully. a. Go to the $PABASE/stumbras/tomcat/conf folder. b. Check if the PID.txt file is present in the folder. The PID.txt file indicates that the process ID of the Tomcat server is registered in the PID.txt file. 15. Stop the Tomcat server. Installation and Configuration February

92 Chapter 3: Installing Avaya OA components a. Enter the command:./opt/bi/.profile. b. Go to the Tomcat server location. Enter the command: cd /opt/bi/stumbras/tomcat/bin. c. Stop the Tomcat server. Enter the command:./shutdown.sh -force. For OA and earlier:./shutdown.sh For OA and later:./stopoareport.sh Installing Avaya OA components on an AIX platform This section describes how to install the following Avaya OA components on an AIX platform: Historical subsystem Real-time subsystem Source-EC subsystem Report subsystem (basic) Data API Utility Depending on the size and resolution of your display terminal, you might have to resize some installation dialog boxes to view all option fields. You can run the install from files copied to the server using FTP. For AIX, you must copy the AixSetup, AixSetup.cp2, and setup.jar files to a temporary folder on a disk drive that is local to the server, not a networked drive. To run the Avaya OA installation process on AIX platforms perform the following:: 1. Ensure that you have completed the prerequisites detailed in Preparing for installation on page Log in as root. 3. To set the monitor display, enter: export DISPLAY=hostname:0.0 where hostname is the name of the server. 4. Put the Avaya OA DVD in the drive and wait about 15 seconds. 92 Installation and Configuration February 2017

93 Installing Avaya OA components on an AIX platform Important:! Important: Install Avaya OA from a DVD drive that is local to the system where you are installing Avaya OA. Installing from a networked DVD drive is not supported. 5. If you are installing the Historical subsystem on the same server as the DB2 client software, or you are installing the Report subsystem, enter the following command to set the environment:. /home/instance_id/.profile where INSTANCE_ID matches the ID used when the DB2 database instance was installed. The default instance ID is db2inst1. 6. If you are installing the Historical subsystem, enter the following commands to set the DB2 environment: export EXTSHM=ON db2set DB2ENVLIST=EXTSHM db2stop db2start 7. Enter the following commands to run the installation: export LANG=en_US mkdir /cdrom (if this folder does not already exist) mount -v cdrfs -r /dev/cd0 /cdrom cd /cdrom./aixsetup After several seconds, the system displays the Initializing wizard window followed by the Welcome dialog box.! Important: You can stop the installation anytime by clicking Cancel before you run the actual installation of files. If you click Cancel, you are asked to confirm your intention to cancel. If you cancel, the system stops the installation and restores the system to previous state. 8. Click Next. The system displays the License Key dialog box. 9. Enter the provided license key for the components purchased. 10. Click Next. The system displays the License Agreement dialog box. 11. Select the I accept the terms in the license agreement option. Important: Installation and Configuration February

94 Chapter 3: Installing Avaya OA components 12. Click Next. The system displays the User Information dialog box. Important: Important: 13. Enter the User ID, User Password, and Group ID. Use a login ID, for example, oauser or biadmin, and password as discussed in Avaya Operational Analyst Release 7.3.x Installation Planning and Prerequisites. This assigns an owner for all Avaya OA files and folders.! Important: The group ID must be the primary group ID for the user ID. 14. Click Next. The system displays the Destination dialog box. By default, the dialog box displays the folder defined for the user ID specified above.! Important: Avaya recommends that you not install Avaya OA on the root file system on AIX servers. Verify that /home (AIX) is not on the root file system disk. If it is on the root file system disk, install the software in a different location. 15. Accept the default folder or you can change the folder, if needed. If you are using an NIS user ID not local to the server, the destination field displays a "/" in the field. You must change this and provide the valid path. 16. To change the location where you want the components installed perform the following: a. Click Browse. 94 Installation and Configuration February 2017

95 Installing Avaya OA components on an AIX platform b. Select the folder. The selected folder must have enough free disk space to accommodate the installed components. It must be on a local disk, not a remote file system. You cannot install Avaya OA software in any system folders such as the following: / (the root directory) /etc /var /tmp /usr/lib /opt/bi 17. Click Next. The system displays the Avaya IC Install Location dialog box. Provide the location where you installed Avaya IC. This location enables the Avaya OA installer to recognize that Avaya IC is installed on the system. If the field is blank, Avaya OA installer cannot install EC and ECB subsystems on the system. 18. Click Next. There might be a long delay before the next dialog box displays. The system displays the Feature Selection dialog box. Installation and Configuration February

96 Chapter 3: Installing Avaya OA components Important: 19. Select the check box corresponding to the component that you want to install. You can install the each component or multiple components in a combination.! Important: After selecting or clearing a check box, there can be a delay of few seconds before the system refreshes the dialog box and you see the check mark or the check mark is cleared. Do not select or clear another check box until the dialog box refreshes and you can see that the check box is selected or cleared. 20. Click Next. If you are installing the Historical subsystem or the Report subsystem, the system displays the Reports Configuration dialog box. If you are not installing the Historical subsystem or Report subsystem, continue with Historical Server Configuration (Step 23). The dialog box displays the Reports Group ID option and Report Writer Group ID option only when you are installing the Historical subsystem. 21. Enter the following information: Field Reports Group ID Report Writer Group ID Description oarpt This is the recommended ID and must match the group ID administered in Avaya Operational Analyst Release 7.3.x Installation Planning and Prerequisites. oawriter This is the recommended ID and must match the group ID administered in Avaya Operational Analyst Release 7.3.x Installation Planning and Prerequisites. 22. Click Next. 96 Installation and Configuration February 2017

97 Installing Avaya OA components on an AIX platform 23. Click OK to accept warning message, if displayed. The system displays the Historical Server Configuration dialog box. The fields that the dialog box displays can vary depending on the components that you selected in the feature selection step. 24. Enter the field values as explained in the following table: Field Historical Subsystem Server Name Historical Database Server Name Do one of the following: Description If you are installing the Historical subsystem, the system displays the name of this server and you cannot change the name. If you are not installing the Historical subsystem, enter the fully qualified domain name of the system where you install the Historical subsystem. Do one of the following: If the Historical database is on the same system where you install the Historical subsystem is, enter the system name. If the Historical database is on a different system than where you install the Historical subsystem is, enter the fully qualified domain name for the system where you install the Historical database is. You must manually create the filegroups or tablespaces on the historical database server before this installation can continue. For more information, see Avaya Operational Analyst Release 7.3.x Installation Planning and Prerequisites. Installation and Configuration February

98 Chapter 3: Installing Avaya OA components Field Please choose a Historical Database Create Historical Tables for these Collection Sources Alarm Services Description Select the appropriate database: DB2 is the only possible selection. Select the collection sources for the historical tables. You can collect data from Avaya IC, CMS, or both depending on what your product license allows. If you are using a backend database, you must create filegroups or tablespaces for Avaya IC, CMS or both before selecting collection sources. For more information, see Avaya Operational Analyst Release 7.3.x Installation Planning and Prerequisites. To send alarm data to the Avaya IC server, click the IC box under Alarm Services. Then enter the fully qualified domain name of the server where you install the Source-EC subsystem is in the Server Name field. 25. Click Next. If you are installing the Historical or Report subsystems, the system displays the Database Configuration dialog box. 98 Installation and Configuration February 2017

99 Installing Avaya OA components on an AIX platform Important:! Important: If you are installing the Historical subsystem on a server that is separate from the Historical database, you must first install the database client software on the server where you install the Historical subsystem is. 26. Enter the fields values as explained in the following table. Use the values from your database installation, which is described in Avaya Operational Analyst Release 7.3.x Installation Planning and Prerequisites. Some of the fields may include default values. Field DB Administrator ID DB Administrator Password OA DB User ID OA DB User Password Administered OS user Value Password for DB Administrator User ID for the Avaya OA database (Avaya OA creates this user ID during a new installation) User password for the Avaya OA database OA Database Name IC DB User ID 1 IC DB User Password 1 IC Repository Database 1 DB Instance Name TCP/IP Port Number The database name specified when DB2 was installed and an instance was created. User ID for the Avaya IC Repository database. This must be an existing Avaya IC user ID, for example, db2inst1. User password for the Avaya IC Repository user ID. Avaya IC Repository database/schema name, for example, repository. Avaya IC and Avaya OA database instance name, for example, db2instl, which is the default. Port number assigned to the database instance creation during the DB2 installation. If you are unsure of the number, check /etc/services and look for the DB2 instance name. The port number is included. OA Database Schema Name Avaya OA database schema name (for example, oaschema). Avaya recommends that you do not change this default name. 1. This field does not display if you do not use Avaya IC as a collection source. Installation and Configuration February

100 Chapter 3: Installing Avaya OA components 27. Click Next. The system displays the DB2 Options dialog box. 28. Enter the field values as explained in the following table. Field Use Existing DB Temp Tablespace Location Syscat Tablespace location Please choose a DB2 Territory Value Determines whether you are using an existing DB2 database. The file location for the temporary tables. The file location for the system catalog. Select the proper territory for your locale. 29. Click Next. The system displays the OA Common Table Spaces dialog box. There might be a long delay before the system displays the next dialog box. 100 Installation and Configuration February 2017

101 Installing Avaya OA components on an AIX platform Important:! Important: If the database is on a back-end database server, the system does not display and table space dialog boxes. Continue with the Step Enter the correct location and the size for each tablespace. For more information, see Avaya Operational Analyst Release 7.3.x Installation Planning and Prerequisites. If the tablespaces does not already exist, you cannot see the check boxes under the Use Existing column, and the Location and Size fields includes default values you can edit. If the tablespaces already exists, you can see that the check boxes under the Use Existing column are selected. You can clear the checkboxes and enter a different location and size in the Location and Size fields. Installation and Configuration February

102 Chapter 3: Installing Avaya OA components 31. Click Next. If the system collects the data from CMS, the system displays the OA CMS Specific dialog box. 32. Enter the correct location and the size for each tablespace. For more information, see Avaya Operational Analyst Release 7.3.x Installation Planning and Prerequisites. If the tablespaces does not already exist, you cannot see the check boxes under the Use Existing column and the Location and Size fields includes default values that you can edit. If the tablespaces already exists, you can see that the check boxes under the Use Existing column are selected. You can clear the checkboxes and enter a different location and size in the Location and Size fields. 33. Click Next 34. If you are not installing the Real-time subsystem, but you selected CMS and did not select IC on the Historical Server Configuration dialog box23, and either: The environment variable BI_DONT_RUN_DBSETUP is undefined, or 102 Installation and Configuration February 2017

103 Installing Avaya OA components on an AIX platform The variable value is not set to "true" the system displays the Historical Database Locale dialog box. 35. Select the appropriate locale for your installation. 36. Click Next. If the system collects the data from Avaya IC, the system displays the OA IC Specific dialog box. Installation and Configuration February

104 Chapter 3: Installing Avaya OA components 37. Enter the correct location and the size for each tablespace. For more information, see Avaya Operational Analyst Release 7.3.x Installation Planning and Prerequisites. If the tablespaces does not already exist, you cannot see the check boxes under the Use Existing column and the Location and Size fields includes default values that you can edit. If the tablespaces already exists, you can see that the check boxes under the Use Existing column are selected. You can clear the checkboxes and enter a different location and size in the Location and Size fields. 38. Click Next. The system can display a warning dialog box about storing the Historical database on one disk. 39. Click OK to acknowledge the warning, if displayed. 40. If you are not installing the Real-time subsystem, but you selected IC on the Historical Server Configuration dialog box (Step 23 of this procedure), and either: The environment variable BI_DONT_RUN_DBSETUP is undefined, or The variable value is not set to "true" the system displays the Historical Database Locale dialog box. 41. Select the appropriate locale for your installation. 42. Click Next. One of the following occurs: If you are not installing the Real-time subsystem, continue with Step Installation and Configuration February 2017

105 Installing Avaya OA components on an AIX platform If you are installing the Real-time subsystem, the system displays the Real-time Configuration dialog box. 43. In the Real Time DB Location field, enter a path that is on a different disk drive from where you install the Avaya OA software is. The drive must have at least 2.2 GB of free disk space available. 44. In the Real Time DB Size(M) field, the only option is Click Next. Installation and Configuration February

106 Chapter 3: Installing Avaya OA components Important:! Important: If you do not have at least 2.2 GB of free disk space to install TimesTen, the system displays a warning message. You cannot continue until at least 2.2 GB of disk space is available. If the environment variable BI_DONT_RUN_DBSETUP is undefined or if the variable value is not set to "true," the system displays the Historical Database Locale dialog box. 46. Select the appropriate locale for your installation. 106 Installation and Configuration February 2017

107 Installing Avaya OA components on an AIX platform 47. Click Next. The system displays the Installation Preview dialog box, which lists the components you have selected. 48. Scroll through the preview dialog box to verify the selected components and configuration data. Installation and Configuration February

108 Chapter 3: Installing Avaya OA components CAUTION:! CAUTION: Do not close the Progress dialog box after you have clicked Next in the following step. If you close the Progress dialog box after the installation has started, the installation will be disrupted. You must contact Avaya support to do a manual cleanup of the installation. 49. Click Next to run the installation. The system displays the Progress dialog box showing the installation progress. 108 Installation and Configuration February 2017

109 Installing Avaya OA components on an AIX platform The installation process can take several minutes. Near the end of the installation, the Progress dialog box can become blank for some time. After the installation is complete, the system displays the Install Complete dialog box. 50. Click Next. The system closes the Install Complete dialog box. Installation and Configuration February

110 Chapter 3: Installing Avaya OA components 51. Close all, but one terminal window and enter: cd / umount /cdrom 52. Press the eject button on the DVD drive, remove the Avaya OA DVD, and store it in a safe location. Verifying the Avaya OA installation on AIX platform CAUTION: 1. Log out of the desktop environment. 2. Log in to the system using an Avaya OA user ID and password. For more information, see Avaya Operational Analyst Release 7.3.x Installation Planning and Prerequisites.! CAUTION: Do not use any Avaya OA commands while logged in as root. Using the root login ID on these commands changes ownership of files and makes them unusable by the Avaya OA user ID. 3. Enter:. /opt/bi/.profile 4. Enter the following command to show what processes are running: pa list The system displays a message similar to the following:. system boot Jan 20 07:54. run-level 4 Jan 20 10:23 4 java. Jan 20 07: id=admb java. Jan 20 07: id=adm0 java. Jan 20 16: id=ams java. Jan 20 07: id=aut java. Jan 20 07: id=schd There should be several Java entries, and these lines should not have an exit code at the end of the line. If there are any exit codes displayed on the Java entries, that process is not running. Escalate the problem to Avaya Technical Support. The id=aut and id=schd only displays when you install the Historical subsystem. 110 Installation and Configuration February 2017

111 Installing Avaya OA components on an AIX platform The recorder entries displays only if you are collecting data from CMS or Avaya IC. Forwarder entries might display on a server that you install the Real-time subsystem. 5. If Avaya OA is not running (mom is not active), enter: pa start all 6. Repeat Step 4 to verify Avaya OA is running. If you are not successful starting Avaya OA, see Avaya Operational Analyst Release 7.3.x Maintenance and Troubleshooting Guide for more troubleshooting information. Installation and Configuration February

112 Chapter 3: Installing Avaya OA components 7. Enter the following command: oalist The system displays a message similar to the following: Subsystems installed Historical Real Time Reports Data API Utility Source-EC Server Names Historical: puoaaix7205 Historical Database: <IP_Address_of_Historical_Database_System> Database information Type: DB2 AdminID: db2inst1 UserID: db2inst1 Instance Name: db2inst1 Port Number: OA DB Name: oadb OA DB Schema Name: oaschema IC UserID: repository IC Repository DB Name: repository Using a Backend/Remote Database IC Historical Tables created DB2 Path: /home/db2inst1 DB2 Library Path: /home/db2inst1/sqllib DB2 Version: 9.5.x User information OA User ID: biadmin Group ID: oaadmin Reports information Reports Group ID: oarpt Report Writer Group ID: oawriter Tomcat Home: /home/biadmin/bi/stumbras/tomcat Tomcat Port: 9080 OA Software information Version Installed: If you have installed the Historical subsystem, use the following commands and the responses to verify that the required services are running. If the services are not running, escalate the problem using the normal channels. 112 Installation and Configuration February 2017

113 Installing Avaya OA components on an AIX platform a. Enter the following command to determine if the Avaya Business Intelligence Service is running: ps -ef grep initsrv The system displays a message similar to the following: root Jan 20? 0:06 /opt/bi/bin/initsrv -n oaadmin -v 30 biadmin :28:00 pts/11 0:00 grep initsrv b. Enter the following command to determine if the ORBacus Naming Service is running: ps -ef grep naming The system displays a message similar to the following: biadmin Jan 20? 6:48 /export/home/biadmin/ jre<version_number>/bin/java -Dooc.naming.port=10000 com.ooc.cosn biadmin :27:35 pts/3 0:00 grep naming 9. If you have installed the Real-time subsystem, use the following commands and responses to verify that the required services are running. If the services are not running, escalate the problem using the normal channels. a. Enter the following command to determine if the Avaya Business Intelligence Service is running: ps -ef grep initsrv The system displays a message similar to the following: root Jan 20? 0:06 /opt/bi/bin/initsrv -n oaadmin -v 30 biadmin :28:00 pts/11 0:00 grep initsrv b. Enter the following command to determine if the ORBacus Naming Service is running: ps -ef grep naming The system displays a message similar to the following: biadmin Jan 20? 6:48 /export/home/biadmin/ jre<version_number>/bin/java -Dooc.naming.port=10000 com.ooc.cosn biadmin :27:35 pts/3 0:00 grep naming Installation and Configuration February

114 Chapter 3: Installing Avaya OA components c. Enter the following command to determine if the TimesTen Data Manager is running: ps -ef grep timesten The system displays a message similar to the following: biadmin :01:34 pts/0 0:00 grep timesten root Jan 20-0:17 /home/biadmin/timesten5.1.34/timesten/ avaya_bi/bin/timestensubd -verbose -id 2 -facility user root Jan 20-0:17 /home/biadmin/timesten5.1.34/timesten/ avaya_bi/bin/timestensubd -verbose -id 1 -facility user root Jan 20-3:35 /home/biadmin/timesten5.1.34/timesten/ avaya_bi/bin/timestensubd -verbose -id 3 -facility user root Jan 20-0:42 /home/biadmin/timesten5.1.34/timesten/ avaya_bi/bin/timestend -fg root Jan 20-0:18 /home/biadmin/timesten5.1.34/timesten/ avaya_bi/bin/timestensubd -verbose -id 0 -facility user 10. If you have installed the Source-EC subsystem, use the following commands and responses to verify that the required services are running. If the services are not running, escalate the problem using the normal channels. a. Enter the following command to determine if the ORBacus Naming Service is running: ps -ef grep naming The system displays a message similar to the following: biadmin Jan 20? 6:48 /export/home/biadmin/ jre<version_number>/bin/java -Dooc.naming.port=10000 com.ooc.cosn biadmin :27:35 pts/3 0:00 grep naming 11. If you have installed the Report subsystem, use the following commands and responses to verify that the required services are running. If the services are not running, escalate the problem using the normal channels. a. Enter the following command to determine if the Avaya Business Intelligence Service is running: ps -ef grep initsrv The system displays a message similar to the following: root Jan 20? 0:06 /opt/bi/bin/initsrv -n oaadmin -v 30 biadmin :28:00 pts/11 0:00 grep initsrv 114 Installation and Configuration February 2017

115 Installing Avaya OA components on an AIX platform b. Enter the following command to determine if the ORBacus Naming Service is running: ps -ef grep naming The system displays a message similar to the following: biadmin Jan 20? 6:48 /export/home/biadmin/ jre<version_number>/bin/java -Dooc.naming.port=10000 com.ooc.cosn biadmin :27:35 pts/3 0:00 grep naming CAUTION: 12. Start the Tomcat server after you configure the Admin client. For more information, see Administration client options on page 168. a. Log in to the system using an Avaya OA user ID and password. For more information, see Avaya Operational Analyst Release 7.3.x Installation Planning and Prerequisites.! CAUTION: Do not use any Avaya OA commands while logged in as root. Using the root login ID on these commands changes ownership of files and makes them unusable by the Avaya OA user ID. b. Enter the command:. /opt/bi/.profile. 13. Go to the Tomcat server location. Enter the command: cd /opt/bi/stumbras/tomcat/bin 14. Start the Tomcat server. Enter the command: For OA and earlier:./startup.sh For OA and later:./startoareport.sh 15. Check the Tomcat server logs to verify that Tomcat is running successfully. a. Go to the $PABASE/stumbras/tomcat/logs/ folder. b. Enter the command: vi catalina.out. Check for the following information in the log file. INFO: Server startup in ms 16. Check if the Tomcat server is running successfully. Enter the following command: ps -eaf grep catalina grep /opt/bi/stumbras/tomcat The system displays a message similar to the following: Installation and Configuration February

116 Chapter 3: Installing Avaya OA components biadmin :27:59 pts/1 1:01 /home/biadmin/jre<version_number>/bin/ java -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager -Djava.util.l ogging.config.file=/opt/bi/stumbras/tomcat/conf/logging.properties -Djava.endors ed.dirs=/opt/bi/stumbras/tomcat/endorsed -classpath :/opt/bi/stumbras/tomcat/bin /bootstrap.jar -Dcatalina.base=/opt/BI/stumbras/tomcat -Dcatalina.home=/opt/BI/s tumbras/tomcat -Djava.io.tmpdir=/opt/BI/stumbras/tomcat/temp org.apache.catalina.startup.bootstrap start 17. Stop the Tomcat server. a. Enter the command:./opt/bi/.profile. b. Go to the Tomcat server location. Enter the command: cd /opt/bi/stumbras/tomcat/bin. c. Stop the Tomcat server. Enter the command: For OA and earlier:./shutdown.sh -force For OA and later:./stopoareport.sh -force 18. Verify that Avaya OA reports are running. a. In a browser window, enter: The system displays the Tomcat Administrative Console. Where: report_server_fqdn is the fully qualified domain name of the server where you install the Report subsystem is. port_number is the port number the system assigns to the Tomcat Administrative Console (for example, 9080). b. In the left pane, click Tomcat Manager. c. Log in to the Tomcat Administrative Console using the following login credentials: UserID: admin Password: admin d. In the Tomcat Web Application Manager page, check for: Display Name Stumbras Running true 116 Installation and Configuration February 2017

117 Installing Avaya OA components on a CMS server - Solaris SPARC Installing Avaya OA components on a CMS server - Solaris SPARC This section describes how to install the following Avaya OA components on a CMS server: Source-CMS subsystem Data API Utility To collect CMS historical data, you must install the Source-CMS subsystem on each CMS server from which you are collecting data. The dialog boxes shown in this section are based on using the CDE interface. If the customer is using the OpenWin interface, the installation dialog boxes appears different. Avaya recommends that you use the CDE interface for installation. CMS R18 is supported from OA onwards. You can run the install from files copied to the server using binary copy mode of FTP. For Solaris, you must copy the SolSetup and setup.jar files to a temporary folder on a local disk drive of the server, not a networked drive. for more information, see Remote installation of CMS data collection software on page 375 for instructions. This section includes the following topics: Installing Avaya OA components - Solaris SPARC on page 117 Configuring time zone offsets on page 122 Installing Informix client SDK library- Solaris SPARC for CMS R16.x and R17.x on page 125 Installing Informix client SDK library on Oracle Solaris for CMS 18 on page 128 Installing Avaya OA components - Solaris SPARC To install Avaya OA components on a CMS server: 1. Log in as root to the CDE on the local CMS system. 2. Put the Avaya OA DVD in the drive and wait about 15 seconds. Installation and Configuration February

118 Chapter 3: Installing Avaya OA components Important:! Important: Install Avaya OA from a DVD drive that is local to the server where you are installing Avaya OA. Installing from a networked DVD drive is not supported. The system displays a file manager window showing the contents of the DVD. If the File Manager window does not open, enter the following commands to run the volume manager: /etc/init.d/volmgt stop /etc/init.d/volmgt start 3. From a terminal window, enter the following commands: cd /cdrom/cdrom0./solsetup The system displays the following Warning dialog box for the Informix client installation not in the requisite folder. Important: The client library is required for OA functioning on the CMS Server. You must install this library for CMS R16.x and later after installing OA. The system does not display this warning while installing OA 7.3 on the CMS R15 server. After you complete installing Avaya OA, install the Informix client SDK libraries. For more information, see Installing Informix client SDK library- Solaris SPARC for CMS R16.x and R17.x on page 125 or Installing Informix client SDK library on Oracle Solaris for CMS 18 on page Click OK. After several seconds, the system displays Initializing wizard window, followed by the Welcome dialog box.! Important: You can stop the installation anytime by clicking Cancel before you run the actual installation of files (see Step 23). If you click Cancel, you are asked to confirm your intention to cancel. If you cancel, the system stops the installation and restores the system to previous state. 118 Installation and Configuration February 2017

119 Installing Avaya OA components on a CMS server - Solaris SPARC 5. Click Next. The License Key dialog box displays. 6. Enter the provided license key for the components purchased. 7. Click Next. The License Agreement dialog box displays. 8. Select I accept the terms in the license agreement. 9. Click Next. The User Information dialog box displays. 10. Enter the User ID, User Password, and Group ID. Use a login ID and password, usually biadmin, as discussed in Avaya Operational Analyst Release 7.3.x Installation Planning and Prerequisites. This assigns an owner for all Avaya OA files and folders. 11. Click Next. The Destination dialog box displays. The Destination dialog box lets you specify the destination for installation of the Avaya OA software. This defaults to the folder defined for the user ID. On a CMS server, you might install the Source-CMS subsystem on the /cms file system instead of the root (/) file system, which is the default location. Contact the CMS administrator when selecting a destination. 12. To change the location where you want the components installed perform the following: a. Click Browse. Installation and Configuration February

120 Chapter 3: Installing Avaya OA components b. Select the folder. The selected folder must have enough free disk space to accommodate the installed components. The folder must be on a local disk, not a remote file system. You cannot install Avaya OA software in any system folders such as the following: / (the root directory) /etc /var /tmp /usr/lib /opt/bi 13. Click Next. There might be a long delay before the next dialog box displays. The Feature Selection dialog box displays. 14. Select Source-CMS Subsystem and, if needed, Data API Utility. 15. Click Next. The Historical Server Configuration dialog box displays. 16. Enter the Historical Subsystem Server Name using the fully qualified domain name of the server where you install the Historical subsystem is. 17. To send alarm data to the Avaya IC server, click the IC box under Alarm Services. Then enter the fully qualified domain name of the server where you install the Source-EC subsystem is in the Server Name field. For an Avaya OA and CMS configuration without Avaya IC, leave these options blank. 120 Installation and Configuration February 2017

121 Installing Avaya OA components on a CMS server - Solaris SPARC 18. Click Next. The CMS Database Configuration dialog box displays. Tip: CAUTION: 19. Enter the informix user ID and password as administered on the CMS server. Tip: If you have not assigned a password, use the passwd informix command to assign a password before you continue. 20. Click Next. 21. The Installation Preview dialog box displays listing the components you have selected. 22. Scroll through the preview dialog box to verify the components you selected.! CAUTION: Do not close the Progress dialog box after you have clicked Next in the following step. If you close the Progress dialog box after the installation has started, you disrupt the installation. You must contact Avaya support to do a manual cleanup of the installation. 23. Click Next to run the installation. The Progress dialog box displays showing the progress of the installation, which takes several minutes. Near the end of the installation, the dialog box goes blank for some time. When the installation is complete, the Install Complete dialog box displays. 24. Click Next. The Install Complete dialog box closes. 25. Close all, but one terminal window and enter: cd / eject cdrom Installation and Configuration February

122 Chapter 3: Installing Avaya OA components 26. Remove the Avaya OA DVD and store it in a safe location. 27. Use the following command and response to verify that the required service is running. If the service is not running, escalate the problem using the normal channels. ps -ef grep CosNaming The system displays a message similar to the following: biadmin Oct 21? 6:48 /export/home/biadmin/jre<version_number>/bin/java -Dooc.naming.port=10000 com.ooc.cosn biadmin :27:35 pts/3 0:00 grep naming Configuring time zone offsets Avaya OA uses data collected from a CMS server to create reports about contact center performance. To correlate data from multiple ACDs (switches), you must configure the time zone on the CMS server to use Greenwich Mean Time (GMT) offsets. You must also configure the CMS server to recognize Daylight Savings Time (DST) rules. In addition, you might have to configure the forwarder files on the CMS server for non standard DST rules. Adjusting the ACD time zone offset does not affect the time as stored in Avaya OA. It is always be the time zone of the switch as adjusted for GMT. This section includes the following topics: Basic CMS time zone settings- Solaris SPARC on page 122 Forwarder file time zone settings on Solaris SPARC on page 123 Basic CMS time zone settings- Solaris SPARC Standard provisioning for a CMS server configures time zones based on geographic region. This configuration automatically compensates for DST rules and converts the internal time of the CMS to GMT. You should verify that the time zone is set correctly on the CMS server. To verify the correct setting of the CMS server time zone perform the following: 1. Log in to the CMS server as root. 122 Installation and Configuration February 2017

123 Installing Avaya OA components on a CMS server - Solaris SPARC 2. Enter the command: vi /etc/default/init The system displays a message similar to the following: /05/26 # # This file is /etc/default/init. /etc/timezone is a symlink to this file. # This file looks like a shell script, but it is not. To maintain # compatibility with old versions of /etc/timezone, some shell constructs # (i.e., export commands) are allowed in this file, but are ignored. # # Lines of this file should be of the form VAR=value, where VAR is one of # TZ, LANG, CMASK, or any of the LC_* environment variables. # TZ=US/Mountain 3. Verify that you set the time zone using a geographic region, similar to what is in the above example. If you have not set the time zone using a geographic region, change the line with geographic regions as in the /usr/share/lib/zoneinfo folders. For example, /usr/ share/lib/zoneinfo/us, where you use the Mountain time zone file. 4. Press Esc. 5. Enter: :wq! This writes and quits the file editor. 6. Enter: /usr/sbin/shutdown -y -i6 -g0 This restarts the CMS server. After the restart you must administer the CMS to change the switch time zone offset for all ACDs reporting to the CMS server. For more information, see the section Changing switch time zone in the chapter "Configuring CMS system settings" in the CMS Administration document. Important:! Important: The administration of switch time zone offsets does not automatically adjust for DST. When DST changes occur, the CMS administrator must readminister the offset value. Forwarder file time zone settings on Solaris SPARC By default, the CMS server uses the standard North American DST rules that apply to the United States and Canada. You do not have to change the configuration if all ACDs are observing the standard North American DST rules. However, you must configure those ACDs on the CMS server that do not observe standard North American DST rules. Installation and Configuration February

124 Chapter 3: Installing Avaya OA components For example, a customer has a CMS server in Chicago which observes standard North American DST rules and ACD number 3 is in Phoenix which does not observe standard North American DST rules. You administer the CMS with an offset of -1 hours for the Phoenix ACD. As Arizona does not observe DST, the ACD is -1 hour behind Chicago during Standard Time and -2 hours behind Chicago during DST. CMS administrators must remember to manually change the offset for this ACD when going from DST to Standard Time and from Standard Time to DST. The administered offset of -1 hour is valid if you administer the ACD for Standard Time, and not -2 hours because you administer the CMS server when DST was in effect. For call data that is forwarded from CMS to Avaya OA, you must configure the CMS server to automatically reset the time zone offsets. This reset is for any ACDs in locations that do not observe standard North American DST rules. You must edit the following property files, which are at $PABASE/data/admin/forwarder on the CMS server, and add two time zone run-time property settings: cmsagent.properties cmscallhistory.properties cmscwc.properties cmsskill.properties cmssynonyms.properties cmsvdn.properties First, you must add the following line to the end of each file to define the local offset from GMT: acdntz=xx where N is the number of the ACD and XX is the offset values, which range from -12 (New Zealand) west to 11 (Bering).! Important: Important: The time zone offset from GMT used with forwarder files is a nonstandard numbering format. Do not confuse these settings with standard GMT offsets. Based on the example above for the Phoenix ACD, you add the following line at the end of each property file on the CMS server: acd3tz=7 where 7 is the number of hours difference between GMT and Phoenix time. In addition, you must set a second run-time property that further defines the DST rules for an ACD. This second run-time property uses the following formats: acdndst=noam acdndst=nodst acdndst=weeu acdndst=officialeu acdndst=mon,week,day,min,mon,week,day,min 124 Installation and Configuration February 2017

125 Installing Avaya OA components on a CMS server - Solaris SPARC where N is the number of the ACD and the values are defined as: NoAm - the North American DST rules (default) NoDST - DST is never observed (no is also valid) WeEu - much of Western Europe, except the United Kingdom OfficialEU - official European Union DST rules mon,week,day,min,mon,week,day,min - an explicit beginning and ending time for DST, where: - the first four values represent the beginning of the alternate DST observance and the last four values represent the end of the alternate DST observance - mon = 0 to 11 (0 = January, 1 = February, and so on) - week = 0 to 4 (0 = first week, 1 = second week, and so on) or -1 (no specific week) - day = 0 to 6 (0 = Sunday, 1 = Monday, and so on) or 0 to 31 (if week = -1) - min = 0 to 1439 minutes after midnight (usually 2AM, which = 120) The example acdndst=3,4,0,120,9,4,0,120 represents DST from 2AM on the last Sunday in April through 2AM on the last Sunday in October. Based on the example above for the Phoenix ACD, you add the following line at the end of each property file on the CMS server: acd3dst=nodst Setting up Main ACD time zone for CMS Set the following properties in each forwarder properties files, for the forwarder to collect data from one or multiple ACDs. You set the following properties even if the ACDs are in the different time zones and follow different DST rules: mainacdtz=<time zone of main acd> mainacddst=<dst rule for main acd> You must set these properties in each forwarder property file. Also, you must set these properties even if the CMS is managing a single or multiple ACD. Installing Informix client SDK library- Solaris SPARC for CMS R16.x and R17.x The installation of Informix client SDK library is the prerequisite and one time procedure that you must run. You install this library on the CMS R16.x and CMS R17.x system where the OA forwarders collects the required CMS Historical data. Installation and Configuration February

126 Chapter 3: Installing Avaya OA components You do not need to install the Informix client SDK library if you have upgraded the CMS R16 to CMS R16.2 or later and CMS R16.1 to CMS R16.2 or later and you have already installed the Informix client SDK library for the earlier Avaya OA release as support for CMS R16. Avaya OA forwarders requires the 32-bit SDK library to connect and retrieve information from the Informix database. Before you install Informix client, note the installation location for Avaya OA. You can find the installation location of Avaya OA by running the command ls -l BI in the /opt folder. The installation location of OA is the parent folder of the BI folder. For example, if /export/home/ biadmin is the output of the above ls command, /export/home/biadmin/ is the actual installation location of Avaya OA. The procedure give below assumes that you install Avaya OA in the /export/home/ biadmin/ folder. If you have different installation folder, replace the /export/home/ biadmin/ occurrence with the actually Avaya OA installation location. To install Informix client SDK library perform the following: 1. Log in as root user to CMS R16 on the Solaris system. 2. Go to the root folder and then run the.profile file. Enter the command:. /opt/bi/.profile. 3. Check if any Avaya OA processes are currently running. Enter the command: pa list all. 4. Stop all OA processes that are running. Enter the command: pa stop all 5. Delete all forwarder log files, if exists in the /opt/bi/data/log/forwarder folder. 6. Go to the /opt folder and create a new subfolder named oa_infx_32lib. The installer installs the Informix 32-bit client SDK libraries in this folder. To install the Informix 32-bit client libraries in any other folder, create a soft link named oa_infx_32lib in the /opt folder. 7. Insert the CMS 17 media in the CD/DVD drive. 8. Go to the /cdrom/cdrom0/csdk_32bit folder. 126 Installation and Configuration February 2017

127 Installing Avaya OA components on a CMS server - Solaris SPARC 9. Run the following command to install the Informix 32-bit client SDK library:./installclientsdk -log <Log_Path_Directory>/install.log If the above command returns an error or unable to find the appropriate JRE version, run the above command with the -javahome option and provide the appropriate path of the JRE version or later../installclientsdk -log <Log_Path_Directory>/install.log -javahome /export/home/biadmin/jre<version_number> The installer starts installing the Informix 32-bit client SDK libraries to the default folder mentioned in the $INFORMIXDIR Windows environment variable. However, if the default folder is different than the /opt/oa_infx_32lib folder, specify the /opt/ oa_infx_32lib folder as a location to install the Informix client SDK libraries. You can also specify the location other than the /opt/oa_infx_32lib folder. But, you must create the soft link by the name oa_infx_32lib in the /opt folder. For OA Release 7.3, 7.3.1, and 7.3.2, Avaya OA installs JRE 1.6.0_07 as part of the Avaya OA installation on the CMS system. Use the installed JRE (JRE HOME: /export/home/biadmin/jre<version_number>) for the CSDK installation or provide the location of the pre installed JRE version or later on the CMS server system for installing the Informix client SDK libraries. 10. Type 1 and press Enter to select the installation type as typical. The typical type installation requires approximately MB of free space on the disk. 11. Type 0 and press Enter to continue the installation. To configure Avaya OA forwarders for the Informix client SDK perform the following: After you successfully install the Informix 32-bit client SDK, perform the following procedure to configure Avaya OA for the Informix client SDK. 1. Log in to the system as an Informix user. Enter the command: su informix. 2. Add a new entry for the oacms_ol in the sqlhosts file located in the /opt/ oa_infx_32lib/etc/ folder. a. Open the sqlhosts file from the /opt/informix/etc/ folder. b. Open the sqlhosts file from the /opt/oa_infx_32lib/etc/ folder. c. From the sqlhosts file in the /opt/informix/etc/ folder, copy the last entry for oacms_ol and add it to the existing entries of the sqlhosts file in the /opt/ oa_infx_32lib/etc/ folder. d. Save the sqlhosts file in the /opt/oa_infx_32lib/etc/ folder. Installation and Configuration February

128 Chapter 3: Installing Avaya OA components To Verify the connection of Avaya OA forwarders with the Informix database: 1. Start all Avaya OA processes. Enter the command: pa start all. 2. Check if all servers are running and does not display the termination and the exit codes for the running forwarders. Enter the command: pa list all. 3. Ensure that there are no specific SQL or Informix errors in the each log files specific to forwarders. Check the forwarder log file in the /opt/bi/data/log/forwarder folder. For example, an error that you can observe in the cmsagenttrc.log file is: ERROR - high: OA fwdcmsagent 1080=hagent:CMSReader: (5) SQL call failed , -1, HY000, [Informix][Informix ODBC Driver]Unspecified System Error = If you did not configure the forwarders, you cannot see the forwarder servers and forwarder log files. You must configure Avaya OA forwarders before performing this procedure. 4. Verify the installed version of the Informix client SDK libraries. Enter the command: check_version csdk. Command output for CMS R16.x: Currently installed version: 3.50.UC4. Command output for CMS R17.0.1, CMS R17.0.2, and CMS R17.0.3: Currently installed version: 3.50.UC9. Installing Informix client SDK library on Oracle Solaris for CMS 18 The installation of Informix client SDK library is the prerequisite and one time procedure that you must run. You run this installation on the CMS R18 system where the OA forwarders collect the required CMS Historical data. You do not need to install the Informix client SDK library if you have already installed the Informix client SDK library. Avaya OA forwarders requires the 32-bit SDK library to connect and retrieve information from the Informix database. 128 Installation and Configuration February 2017

129 Installing Avaya OA components on a CMS server - Solaris SPARC Before you install Informix client, note the installation location for Avaya OA. You can find the installation location of Avaya OA by running the command ls -l BI in the /opt folder. The installation location of OA is the parent folder of the BI folder. For example, if /export/home/ biadmin/bi is the output of the above ls command, /export/home/biadmin/ is the actual installation location of Avaya OA. The procedure give below assumes that you installed Avaya OA in the /export/home/ biadmin/ folder. If you have different installation folder, replace the /export/home/ biadmin/ occurrence with the actually Avaya OA installation location. Although user selects OA installation folder other than default, the system always creates /opt/bi as a link to actual OA folder. To install Informix client SDK library: 1. Log in as root user to CMS R18 on the RHEL system. 2. Go to the root folder and then run the.profile file. Enter the command:. /opt/bi/.profile. 3. Check if any Avaya OA processes are currently running. Enter the command: pa list all. 4. Stop all OA processes that are running. Enter the command: pa stop all 5. Delete all forwarder log files, if exists in the /opt/bi/data/log/forwarder folder. 6. Go to the /opt folder and create a new subfolder named oa_infx_32lib. The installer installs the Informix 32-bit client SDK libraries in this folder. To install the Informix 32-bit client libraries in any other folder, create a soft link named oa_infx_32lib in the /opt folder. 7. Go to the CSDK folder: a. If you deployed CMS on the virtual system, go to the /storage/cms_dvd/csdk folder. b. If you deploy CMS on a physical system, insert the CD/DVD and go the location / cdrom/cdrom0/csdk. 8. Extract the Client SDK clientsdk.4.10.uc2de.sol.tar.gz file using the following command: gunzip clientsdk.4.10.uc2de.sol.tar.gz tar -xf clientsdk.4.10.uc2de.sol.tar 9. Run the following command to install the Informix 32-bit client SDK library:./installclientsdk You can also specify the location other than the /opt/oa_infx_32lib folder. But, you must create the soft link by the name oa_infx_32lib in the /opt folder. Installation and Configuration February

130 Chapter 3: Installing Avaya OA components 10. In the Introduction page, press Enter to continue the installation. 11. In the License Agreement page, type 1 and press Enter to continue the installation. 12. In the Installation Location page, provide the path of the install location. The default install path is /opt/informix. To install on the default path type 1 and press Enter to continue. To install Informix in another location: a. Specify the folder path and press Enter. The install screen will show the new path that you entered. b. To confirm, type Y and press Enter. To install the Informix 32-bit client libraries in any other folder, create a soft link named oa_infx_32lib in the /opt folder. 13. In the Choose Product Features page, press Enter to continue. The typical type installation requires approximately 89.1 MB of free space on the disk. 14. In the Host Name page, the installer detects the host name of the system and displays it as the default value. 15. Press Enter to continue with the default host name of the CMS system. 16. In the Specify Apache Port Number page, press Enter to continue with the default port number of the Apache webserver. The default Port Number is In the Security Features page, type No. 18. Press Enter to continue. The Installation Summary page displays the options selected for the CMS R18 installation. You can type Back to go to the previous step or type quit to cancel the installation. 19. Press Enter to continue. 20. After the installation completes, the Installation Complete page is displayed. Press Enter to finish the installation. To configure Avaya OA forwarders for the Informix client SDK: After you successfully install the Informix 32-bit client SDK, perform the following procedure to configure Avaya OA for the Informix client SDK. 1. Log in to the system as an Informix user. Enter the command: su - informix. 2. Add a new entry for the oacms_ol in the sqlhosts file located in the /opt/ oa_infx_32lib/etc/ folder. a. Open the sqlhosts file from the /opt/informix/etc/ folder. b. Goto /opt/oa_infx_32lib/etc/ folder. 130 Installation and Configuration February 2017

131 Installing Avaya OA components on a CMS server - Solaris SPARC c. Create a copy sqlhosts.std file and rename it to sqlhosts file. d. Open the sqlhosts file from the /opt/oa_infx_32lib/etc/ folder. e. From the sqlhosts file in the /opt/informix/etc/ folder, copy the last entry for oacms_ol and add it to the existing entries of the sqlhosts file in the /opt/ oa_infx_32lib/etc/ folder. f. Save the sqlhosts file in the /opt/oa_infx_32lib/etc/ folder. To Verify the connection of Avaya OA forwarders with the Informix database: 1. Log in as biadmin user. 2. Go to the root folder and then run following command:./opt/bi/.profile. 3. Type echo $INFORMIXDIR. Ensure the output of the above command displays /opt/oa_infx_32lib. 4. Start all Avaya OA processes. Enter the command: pa start all. 5. Check if all servers are running and does not display the termination and the exit codes for the running forwarders. Enter the command: pa list all. 6. Ensure that there are no specific SQL or Informix errors in the each log files specific to forwarders. Check the forwarder log file in the /opt/bi/data/log/forwarder folder. For example, an error that you can observe in the cmsagenttrc.log file is: ERROR - high: OA fwdcmsagent 1080=hagent:CMSReader: (5) SQL call failed , -1, HY000, [Informix][Informix ODBC Driver]Unspecified System Error = If you did not configure the forwarders, you cannot see the forwarder servers and forwarder log files. You must configure Avaya OA forwarders before performing this procedure. 7. Verify the installed version of the Informix client SDK libraries. Enter the command: check_version csdk. Command output: Currently installed version: 4.10.UC2DE. Installation and Configuration February

132 Chapter 3: Installing Avaya OA components Installing Avaya OA components on a CMS server for RHEL This section describes how to install the following Avaya OA components on RHEL platform: Source - CMS Subsystem Data API Utility You can install Avaya OA either by using CD/DVD or by copying the installation files to a folder on the CMS server. If you are installing Avaya OA from CD/DVD, the location of the installation files is cdrom/ cdrom0. Avaya OA only supports installing the software from the local CD/DVD drive and does not support installing the software from the CD/DVD drive in the network. If you are installing Avaya OA from a folder on the CMS server, the location of the installation files is the folder where you stored the installation files. The dialog boxes shown in this section are based on using the X11 server installed on a system from where you run the OA installer. From OA onwards, CMS 17.0.x is supported on RHEL platform. You can run the install from files copied to the server using binary copy mode of SFTP. For RHEL, you must copy the LinSetup and setup.jar files to a temporary folder on a disk drive that is local to the server, not a drive in the network. You must also reset the permissions on Linsetup using the chmod +x LinSetup command. See Remote installation of CMS data collection software on page 375 for instructions. CMS 18 is supported on RHEL platform from OA onwards. This section includes the following topics: Installing Avaya OA components - RHEL on page 133 Configuring time zone offsets on page 141 Installing Informix client SDK library on RHEL for CMS 16.x and 17.x on page 145 Installing Informix client SDK library on RHEL for CMS 18 on page Installation and Configuration February 2017

133 Installing Avaya OA components on a CMS server for RHEL Installing Avaya OA components - RHEL To install Avaya OA components on a CMS server: 1. Log in as root to the CDE on the local CMS system. 2. Change the folder to the location from where you want to install Avaya OA. 3. From a terminal window, enter the following commands:./linsetup The system displays the following Warning dialog box for the Informix client installation not in the requisite folder. The client library is required for OA functioning on the CMS Server. You must install this library for CMS R16.x and later after installing OA. After you complete installing Avaya OA, install the Informix client SDK libraries. For more information, see Installing Informix client SDK library on RHEL for CMS 16.x and 17.x on page 145 or Installing Informix client SDK library on RHEL for CMS 18 on page Click OK. After several seconds, the system displays Initializing wizard window, followed by the Welcome dialog box. Important:! Important: You can stop the installation any time by clicking Cancel before you run the actual installation of files (see Step 23). If you click Cancel, you are asked to confirm your intention to cancel. If you cancel, the installation is terminated and the system is restored to its previous state. 5. Click Next. The License Key dialog box displays. 6. Enter the provided license key for the components purchased. 7. Click Next. The License Agreement dialog box displays. 8. Select I accept the terms in the license agreement. Installation and Configuration February

134 Chapter 3: Installing Avaya OA components 9. Click Next. The User Information dialog box displays. 10. Enter the User ID, User Password, and Group ID. Use a login ID and password, usually biadmin, as discussed in Avaya Operational Analyst Release 7.3.x Installation Planning and Prerequisites. This assigns an owner for all Avaya OA files and folders. 11. Click Next. The Destination dialog box displays. The Destination dialog box lets you to specify the destination for installation of the Avaya OA software. This defaults to the folder defined for the user ID. On a CMS server, you might install the Source-CMS subsystem on the /cms file system instead of the root (/) file system, which is the default location. Contact the CMS administrator when selecting a destination. 12. To change the location where you want the components installed perform the following: a. Click Browse. b. Select the folder. The selected folder must have sufficient free disk space to accommodate the installed components. The folder must be on a local disk, not a remote file system. You cannot install Avaya OA software in any system folders such as the following: "/bin", "/cdrom", "/dev", 134 Installation and Configuration February 2017

135 Installing Avaya OA components on a CMS server for RHEL "/etc", "/lib", "/mnt", "/sbin", "/tmp", "/usr", "/var", "/opt/bi", "/boot", "/root", "/proc", "/media", "/media", "/selinux" 13. Click Next. There may be a long delay before the next dialog box displays. The Feature Selection dialog box displays. 14. Select Source-CMS Subsystem and, if needed, Data API Utility. Installation and Configuration February

136 Chapter 3: Installing Avaya OA components Important:! Important: You can install individual components or multiple components in a combination. However, if you are installing Data API Utility, you must select the Source - CMS Subsystem option. 15. Click Next. The Historical Server Configuration dialog box displays. 16. Enter the Historical Subsystem Server Name using the fully qualified domain name of the server where you install the Historical subsystem is. 17. To send alarm data to the Avaya IC server, click the IC box under Alarm Services, and enter the fully qualified domain name of the server where you install the Source-EC subsystem in the Server Name field. For an Avaya OA and CMS configuration without Avaya IC, leave these options blank. 136 Installation and Configuration February 2017

137 Installing Avaya OA components on a CMS server for RHEL 18. Click Next. The system displays the dialog box for specifying the CMS user ID and password. Installation and Configuration February

138 Chapter 3: Installing Avaya OA components 19. Click Next. The Installation Preview dialog box displays listing the components you have selected. CAUTION: 20. Scroll through the preview dialog box to verify the components you selected.! CAUTION: Do not close the Progress dialog box after you click Next in the following step. If you close the Progress dialog box after the installation has started, you disrupt the installation. You must contact Avaya support to do a manual cleanup of the installation. 21. Click Next to start the installation. The Progress dialog box displays showing the progress of the installation, which takes several minutes. Near the end of the installation, the dialog box goes blank for some time. When the installation is complete, the Install Complete dialog box displays. 22. Click Next. The Install Complete dialog box closes. 23. Close all, but one terminal window and enter: cd / eject cdrom 138 Installation and Configuration February 2017

139 Installing Avaya OA components on a CMS server for RHEL 24. Remove the Avaya OA DVD and store it in a safe location. 25. Use the following command and response to verify that the required service is running. If the service is not running, escalate the problem using the normal channels. ps -ef grep CosNaming The system displays a message similar to the following: root :12? 00:00:00 /export/home/biadmin/ jre<version_number>/bin/java com.ooc.cosnaming.server -IIOPport Verifying the Avaya OA installation on the CMS server with RHEL platform CAUTION: 1. Log out of the desktop environment. 2. Log in to the system using an Avaya OA user ID and password. For more information, see Avaya Operational Analyst Release 7.3.x Installation Planning and Prerequisites.! CAUTION: Do not use any Avaya OA commands while logged in as root. Using the root login ID on these commands changes ownership of files and makes them unusable by the Avaya OA user ID. 3. Enter:. /opt/bi/.profile 4. Enter the following command to determine if the Avaya Business Intelligence Service is running: ps -ef grep initsrv The system displays a message similar to the following: root :12? 00:00:00 /opt/bi/bin/initsrv -n oaadmin -v Enter the following command to determine if the ORBacus Naming Service is running: ps -ef grep CosNaming The system displays a message similar to the following: root :12? 00:00:00 /export/home/biadmin/ jre<version_number>/bin/java com.ooc.cosnaming.server -IIOPport Installation and Configuration February

140 Chapter 3: Installing Avaya OA components 6. Enter the following command to show what processes are running: pa list The system displays a message similar to the following: (cmsjune74)-(root)=# pa list all. system boot Oct 1 17:13. run-level 4 Oct 1 17:13 4 java. Oct 1 17:13 old id=admb java. Oct 1 17:13 old id=adm0 java. Oct 1 17:13 old id=ams There should be several Java entries, and these lines should not have an exit code at the end of the line. If there are any exit codes displayed on the Java entries, that process is not running. Escalate the problem to Avaya Technical Support. The id=aut and id=schd only displays when you install the Historical subsystem. The recorder entries display only if you are collecting data from CMS or Avaya IC. Forwarder entries might display on a server that has the Real-time subsystem installed. 7. If you get the message mom is not active, enter: pa start all 8. Repeat Step 6 to verify Avaya OA is running. If you are not successful starting Avaya OA, see Avaya Operational Analyst Release 7.3.x Maintenance and Troubleshooting Guide for more troubleshooting information. 140 Installation and Configuration February 2017

141 Installing Avaya OA components on a CMS server for RHEL 9. Enter the following command: oalist The system displays a message similar to the following: Subsystems installed Data API Utility Source-CMS Server Names Historical: icdev84 Database information Type: UNSET User information CMS ID: informix OA User ID: biadmin Group ID: oaadmin OA Software information Version Installed: Configuring time zone offsets Avaya OA uses data collected from a CMS server to create reports about contact center performance. To correlate data from multiple ACDs (switches), you must configure the time zone configuration on the CMS server to use Greenwich Mean Time (GMT) offsets. You configure the time zone configuration to recognize Daylight Savings Time (DST) rules. In addition, you might configure the forwarder files on the CMS server for non standard DST rules. Adjusting the ACD time zone offset does not affect the time as stored in Avaya OA. It is always be the time zone of the switch as adjusted for GMT. This section includes the following topics: Basic CMS country and time zone settings- RHEL on page 141 Forwarder file time zone settings on page 143 Basic CMS country and time zone settings- RHEL Standard provisioning for a CMS server configures time zones based on geographic region. This configuration automatically compensates for DST rules and converts the internal time of the CMS to GMT. You should verify that the time zone is set correctly on the CMS server. This section contains the following topics: Setting the country on page 142 Setting the time zone on page 142 Installation and Configuration February

142 Chapter 3: Installing Avaya OA components Setting the country To set the country: 1. Log in to the CMS server as root. 2. Enter the command: vi /etc/sysconfig/clock The system displays a message similar to the following: ZONE="America/New_York" 3. Verify that you set the time zone using a geographic region, similar to what is in the above example. If you have not set the time zone using a geographic region, change the line with geographic regions as in the /usr/share/zoneinfo folders. For example, /usr/ share/zoneinfo/us, where you use the Mountain time zone file. 4. Press Esc. 5. Enter: :wq! This writes and quits the file editor. 6. Enter: /usr/sbin/shutdown -r now This restarts the CMS server. You must administer the CMS to change the switch time zone offset for all ACDs reporting to the CMS server. To administer this option, see the section Changing switch time zone in the chapter "Configuring CMS system settings" in the CMS Administration document for your CMS release. Important:! Important: The administration of switch time zone offsets does not automatically adjust for DST. When DST changes occur, the CMS administrator must readminister the offset value. Setting the time zone To set the time zone: 1. Log in to the system as root. 2. Check which time zone your system is currently using. Enter: date The output of the date command is in the following example: Mon 17 Jan :15:08 PM PST In this example, the current time zone of the system is PST. 142 Installation and Configuration February 2017

143 Installing Avaya OA components on a CMS server for RHEL 3. Change to the folder /usr/share/zoneinfo. This folder has a list of time zone regions. Choose the most appropriate region. if you live in Canada or United States of America, this folder is the America folder. 4. Back up the previous time zone configuration by copying it to a different location. Enter: mv /etc/localtime /etc/localtime-old 5. Create a symbolic link to the appropriate time zone from /etc/localtime. For example: ln -sf /usr/share/zoneinfo/us/mountain /etc/localtime 6. If you have the rdate utility, update the current system time. For example: /usr/bin/rdate -s time-a.nist.gov 7. Set the ZONE entry in the file /etc/sysconfig/clock file. For example: America/Los_Angeles 8. Set the hardware clock. Enter: /sbin/hwclock --systohc Forwarder file time zone settings By default, the CMS server uses the standard North American DST rules that apply to the United States and Canada. You do not have to change the configuration if all ACDs are observing the standard North American DST rules. However, you must configure those ACDs on the CMS server that do not observe standard North American DST rules. For example, a customer has a CMS server in Chicago which observes standard North American DST rules and ACD number 3 is in Phoenix which does not observe standard North American DST rules. You administer the CMS with an offset of -1 hours for the Phoenix ACD. As Arizona does not observe DST, the ACD is -1 hour behind Chicago during Standard Time and -2 hours behind Chicago during DST. CMS administrators must remember to manually change the offset for this ACD when going from DST to Standard Time and from Standard Time to DST. The administered offset of -1 hour is valid if you administer the ACD for Standard Time, and not -2 hours because you administer the CMS server when DST was in effect. For call data that is forwarded from CMS to Avaya OA, you must configure the CMS server to automatically reset the time zone offsets. This reset is for any ACDs in locations that do not observe standard North American DST rules. You must edit the following property files, which are at $PABASE/data/admin/forwarder on the CMS server, and add two time zone run-time property settings: cmsagent.properties cmscallhistory.properties cmscwc.properties Installation and Configuration February

144 Chapter 3: Installing Avaya OA components cmsskill.properties cmssynonyms.properties cmsvdn.properties First, you must add the following line to the end of each file to define the local offset from GMT: acdntz=xx where N is the number of the ACD and XX is the offset values, which range from -12 (New Zealand) west to 11 (Bering).! Important: Important: The time zone offset from GMT used with forwarder files is a nonstandard numbering format. Do not confuse these settings with standard GMT offsets. Based on the example above for the Phoenix ACD, you add the following line at the end of each property file on the CMS server: acd3tz=7 where 7 is the number of hours difference between GMT and Phoenix time. In addition, you must set a second run-time property that further defines the DST rules for an ACD. This second run-time property uses the following formats: acdndst=noam acdndst=nodst acdndst=weeu acdndst=officialeu acdndst=mon,week,day,min,mon,week,day,min where N is the number of the ACD and the values are defined as: NoAm - the North American DST rules (default) NoDST - DST is never observed (no is also valid) WeEu - much of Western Europe, except the United Kingdom OfficialEU - official European Union DST rules mon,week,day,min,mon,week,day,min - an explicit beginning and ending time for DST, where: - the first four values represent the beginning of the alternate DST observance and the last four values represent the end of the alternate DST observance - mon = 0 to 11 (0 = January, 1 = February, and so on) - week = 0 to 4 (0 = first week, 1 = second week, and so on) or -1 (no specific week) - day = 0 to 6 (0 = Sunday, 1 = Monday, and so on) or 0 to 31 (if week = -1) 144 Installation and Configuration February 2017

145 Installing Avaya OA components on a CMS server for RHEL - min = 0 to 1439 minutes after midnight (usually 2AM, which = 120) The example acdndst=3,4,0,120,9,4,0,120 represents DST from 2AM on the last Sunday in April through 2AM on the last Sunday in October. Based on the example above for the Phoenix ACD, you add the following line at the end of each property file on the CMS server: acd3dst=nodst Setting up Main ACD time zone for CMS Set the following properties in each forwarder properties files, for the forwarder to collect data from one or multiple ACDs. You set the following properties even if the ACDs are in the different time zones and follow different DST rules: mainacdtz=<time zone of main acd> mainacddst=<dst rule for main acd> You must set these properties in each forwarder property file. Also, you must set these properties even if the CMS is managing a single or multiple ACD. Installing Informix client SDK library on RHEL for CMS 16.x and 17.x The installation of Informix client SDK library is the prerequisite and one time procedure that you must run. You run this installation on the CMS R16.x or R17.x system where the OA forwarders collect the required CMS Historical data. You do not need to install the Informix client SDK library if you have upgraded the CMS R17 to R17 FP4 and you have already installed the Informix client SDK library for the earlier Avaya OA release as support for CMS R17. Avaya OA forwarders requires the 32-bit SDK library to connect and retrieve information from the Informix database. Before you install Informix client, note the installation location for Avaya OA. You can find the installation location of Avaya OA by running the command ls -l BI in the /opt folder. The installation location of OA is the parent folder of the BI folder. For example, if /export/home/ biadmin/bi is the output of the above ls command, /export/home/biadmin/ is the actual installation location of Avaya OA. The procedure give below assumes that you installed Avaya OA in the /export/home/ biadmin/ folder. If you have different installation folder, replace the /export/home/ biadmin/ occurrence with the actually Avaya OA installation location. Although user selects OA installation folder other than default, the system always creates /opt/bi as a link to actual OA folder. Installation and Configuration February

146 Chapter 3: Installing Avaya OA components To install Informix client SDK library: 1. Log in as root user to CMS R17 on the RHEL system. 2. Go to the root folder and then run the.profile file. Enter the command:. /opt/bi/.profile. 3. Check if any Avaya OA processes are currently running. Enter the command: pa list all. 4. Stop all OA processes that are running. Enter the command: pa stop all 5. Delete all forwarder log files, if exists in the /opt/bi/data/log/forwarder folder. 6. Go to the /opt folder and create a new subfolder named oa_infx_32lib. The installer installs the Informix 32-bit client SDK libraries in this folder. To install the Informix 32-bit client libraries in any other folder, create a soft link named oa_infx_32lib in the /opt folder. 7. Go to the CSDK_32bit folder: a. If you deployed CMS on the virtual system, go to the /storage/cms_dvd/ CSDK_32bit folder. b. If you deploy CMS on a physical system, insert the CD/DVD and go the location / cdrom/cdrom0/csdk_32bit. 8. Run the following command to install the Informix 32-bit client SDK library:./installclientsdk -log /opt/oa_infx_32lib/install.log If the above command returns an error or unable to find the appropriate JRE version, run the above command with the -javahome option and provide the appropriate path of the JRE version from 1.4.x to 1.7.x. For example:./installclientsdk -log /opt/oa_infx_32lib/install.log -javahome / <path_where_jre_is_installed_or_extracted>/jre<version_number> The installer starts installing the Informix 32-bit client SDK libraries to the default folder / opt/informix. However, if the default folder is different than the /opt/ oa_infx_32lib folder, specify the /opt/oa_infx_32lib folder as a location to install the Informix client SDK libraries. You can also specify the location other than the /opt/oa_infx_32lib folder. But, you must create the soft link by the name oa_infx_32lib in the /opt folder. Avaya OA installs the following JRE versions based on the release OA release: 146 Installation and Configuration February 2017

147 Installing Avaya OA components on a CMS server for RHEL For OA 7.3.3, JRE 1.6.0_07 is installed as part of the Avaya OA installation on the CMS system. Use the installed JRE (JRE HOME: /export/home/biadmin/ jre<version_number>) for the CSDK installation or provide the location of the pre installed JRE version or later on the CMS server system for installing the Informix client SDK libraries. For OA and later JRE 1.8.x is installed as part of the Avaya OA installation on the CMS system. If you are installing Informix client SDK libraries on a CMS 16 or CMS 17 system with OA or later, then you must install or extract JRE 1.6.x or 1.7.x in a temporary folder and use the temporary folder path as a JRE Home for installing the client SDK../installclientsdk -log /opt/oa_infx_32lib/install.log -javahome /<path_where_jre_is_installed_or_extracted>/ jre<version_number> 9. In the Welcome page, type 1 and press Enter to continue the installation. 10. In the License Agreement page, type 1 and press Enter to continue the installation. 11. In the Install Location page, type 1 and press Enter to continue the installation with the default install path. 12. Type 1 and press Enter to select the installation type as typical. The typical type installation requires approximately 89.1 MB of free space on the disk. 13. Type 0 and press Enter to continue the installation. 14. Type 1 and press Enter to continue. 15. Type 1 and press Enter to run the installation. 16. After the installation completes, type 3 and press Enter to finish the installation. To configure Avaya OA forwarders for the Informix client SDK: After you successfully install the Informix 32-bit client SDK, perform the following procedure to configure Avaya OA for the Informix client SDK. 1. Log in to the system as an Informix user. Enter the command: su informix. 2. Add a new entry for the oacms_ol in the sqlhosts file located in the /opt/ oa_infx_32lib/etc/ folder. a. Open the sqlhosts file from the /opt/informix/etc/ folder. b. Open the sqlhosts file from the /opt/oa_infx_32lib/etc/ folder. c. From the sqlhosts file in the /opt/informix/etc/ folder, copy the last entry for oacms_ol and add it to the existing entries of the sqlhosts file in the /opt/ oa_infx_32lib/etc/ folder. d. Save the sqlhosts file in the /opt/oa_infx_32lib/etc/ folder. Installation and Configuration February

148 Chapter 3: Installing Avaya OA components To Verify the connection of Avaya OA forwarders with the Informix database: 1. Log in as biadmin user. 2. Go to the root folder and then run following command:./opt/bi/.profile. 3. Type echo $INFORMIXDIR. Ensure the output of the above command displays /opt/oa_infx_32lib. 4. Open the /opt/bi/data/admin/odbc.ini file and change the value of the Driver property as follows: - Old Value: Driver=/opt/informix/lib/cli/iclit09b.so - New Value: Driver=/opt/oa_infx_32lib/lib/cli/iclit09b.so Also change the value of the InstallDir variable in the ODBC section to the SDK install folder: InstallDir=/opt/oa_infx_32lib. 5. Start all Avaya OA processes. Enter the command: pa start all. 6. Check if all servers are running and does not display the termination and the exit codes for the running forwarders. Enter the command: pa list all. 7. Ensure that there are no specific SQL or Informix errors in the each log files specific to forwarders. Check the forwarder log file in the /opt/bi/data/log/forwarder folder. For example, an error that you can observe in the cmsagenttrc.log file is: ERROR - high: OA fwdcmsagent 1080=hagent:CMSReader: (5) SQL call failed , -1, HY000, [Informix][Informix ODBC Driver]Unspecified System Error = If you did not configure the forwarders, you cannot see the forwarder servers and forwarder log files. You must configure Avaya OA forwarders before performing this procedure. 8. Verify the installed version of the Informix client SDK libraries. Enter the command: check_version csdk. Command output: Currently installed version: 3.50.UC Installation and Configuration February 2017

149 Installing Avaya OA components on a CMS server for RHEL Installing Informix client SDK library on RHEL for CMS 18 The installation of Informix client SDK library is the prerequisite and one time procedure that you must run. You run this installation on the CMS R18 system where the OA forwarders collect the required CMS Historical data. You do not need to install the Informix client SDK library if you have already installed the Informix client SDK library. Avaya OA forwarders requires the 32-bit SDK library to connect and retrieve information from the Informix database. Before you install Informix client, note the installation location for Avaya OA. You can find the installation location of Avaya OA by running the command ls -l BI in the /opt folder. The installation location of OA is the parent folder of the BI folder. For example, if /export/home/ biadmin/bi is the output of the above ls command, /export/home/biadmin/ is the actual installation location of Avaya OA. The procedure give below assumes that you installed Avaya OA in the /export/home/ biadmin/ folder. If you have different installation folder, replace the /export/home/ biadmin/ occurrence with the actually Avaya OA installation location. Although user selects OA installation folder other than default, the system always creates /opt/bi as a link to actual OA folder. To install Informix client SDK library: 1. Log in as root user to CMS R18 on the RHEL system. 2. Go to the root folder and then run the.profile file. Enter the command:. /opt/bi/.profile. 3. Check if any Avaya OA processes are currently running. Enter the command: pa list all. 4. Stop all OA processes that are running. Enter the command: pa stop all 5. Delete all forwarder log files, if exists in the /opt/bi/data/log/forwarder folder. 6. Go to the /opt folder and create a new subfolder named oa_infx_32lib. The installer installs the Informix 32-bit client SDK libraries in this folder. To install the Informix 32-bit client libraries in any other folder, create a soft link named oa_infx_32lib in the /opt folder. 7. Go to the CSDK folder: a. If you deployed CMS on the virtual system, go to the /storage/cms_dvd/csdk folder. Installation and Configuration February

150 Chapter 3: Installing Avaya OA components b. If you deploy CMS on a physical system, insert the CD/DVD and go the location / cdrom/cdrom0/csdk. 8. Extract the Client SDK clientsdk.4.10.uc2de.linux.tar.gz file using the following command: gunzip clientsdk.4.10.uc2de.linux.tar.gz tar -xf clientsdk.4.10.uc2de.linux.tar 9. Run the following command to install the Informix 32-bit client SDK library:./installclientsdk You can also specify the location other than the /opt/oa_infx_32lib folder. But, you must create the soft link by the name oa_infx_32lib in the /opt folder. 10. In the Introduction page, press Enter to continue the installation. 11. In the License Agreement page, type 1 and press Enter to continue the installation. 12. In the Installation Location page, provide the path of the install location. The default install path is /opt/informix. To install on the default path type 1 and press Enter to continue. To install Informix in another location: a. Specify the folder path and press Enter. The install screen will show the new path that you entered. b. To confirm, type Y and press Enter. To install the Informix 32-bit client libraries in any other folder, create a soft link named oa_infx_32lib in the /opt folder. 13. In the Choose Product Features page, press Enter to continue. The typical type installation requires approximately 89.1 MB of free space on the disk. 14. In the Host Name page, the installer detects the host name of the system and displays it as the default value. 15. Press Enter to continue with the default host name of the CMS system. 16. In the Specify Apache Port Number page, press Enter to continue with the default port number of the Apache webserver. The default Port Number is In the Security Features page, type No. 18. Press Enter to continue. The Installation Summary page displays the options selected for the CMS R18 installation. You can type Back to go to the previous step or type quit to cancel the installation. 19. Press Enter to continue. 150 Installation and Configuration February 2017

151 Installing Avaya OA components on a CMS server for RHEL 20. After the installation completes, the Installation Complete page is displayed. Press Enter to finish the installation. To configure Avaya OA forwarders for the Informix client SDK: After you successfully install the Informix 32-bit client SDK, perform the following procedure to configure Avaya OA for the Informix client SDK. 1. Log in to the system as an Informix user. Enter the command: su - informix. 2. Add a new entry for the oacms_ol in the sqlhosts file located in the /opt/ oa_infx_32lib/etc/ folder. a. Open the sqlhosts file from the /opt/informix/etc/ folder. b. Goto /opt/oa_infx_32lib/etc/ folder. c. Create a copy sqlhosts.std file and rename it to sqlhosts file. d. Open the sqlhosts file from the /opt/oa_infx_32lib/etc/ folder. e. From the sqlhosts file in the /opt/informix/etc/ folder, copy the last entry for oacms_ol and add it to the existing entries of the sqlhosts file in the /opt/ oa_infx_32lib/etc/ folder. f. Save the sqlhosts file in the /opt/oa_infx_32lib/etc/ folder. To Verify the connection of Avaya OA forwarders with the Informix database: 1. Log in as biadmin user. 2. Go to the root folder and then run following command:./opt/bi/.profile. 3. Type echo $INFORMIXDIR. Ensure the output of the above command displays /opt/oa_infx_32lib. 4. Start all Avaya OA processes. Enter the command: pa start all. 5. Check if all servers are running and does not display the termination and the exit codes for the running forwarders. Enter the command: pa list all. 6. Ensure that there are no specific SQL or Informix errors in the each log files specific to forwarders. Check the forwarder log file in the /opt/bi/data/log/forwarder folder. For example, an error that you can observe in the cmsagenttrc.log file is: Installation and Configuration February

152 Chapter 3: Installing Avaya OA components ERROR - high: OA fwdcmsagent 1080=hagent:CMSReader: (5) SQL call failed , -1, HY000, [Informix][Informix ODBC Driver]Unspecified System Error = If you did not configure the forwarders, you cannot see the forwarder servers and forwarder log files. You must configure Avaya OA forwarders before performing this procedure. 7. Verify the installed version of the Informix client SDK libraries. Enter the command: check_version csdk. Command output: Currently installed version: 4.10.UC2DE. Uninstalling Informix client SDK library This section provides information on the following: Uninstalling Informix client SDK library on CMS 16.x and 17.x on page 152 Uninstalling Informix client SDK library on CMS 18 on page 153 Uninstalling Informix client SDK library on CMS 16.x and 17.x To remove the Informix client SDK library: 1. Stop all Avaya OA forwarders. Enter the command: pa stop all. 2. Go to the /opt/oa_infx_32lib/uninstall_csdk folder and enter the following command: /export/home/biadmin/jre<version_number>/bin/java -jar uninstall.jar. The /export/home/biadmin/ is the location where you install Avaya OA is. 3. Delete the /opt/oa_infx_32lib folder after the removal is complete. 152 Installation and Configuration February 2017

153 Installing and testing the Report client Uninstalling Informix client SDK library on CMS 18 To remove the Informix client SDK library: 1. Stop all Avaya OA forwarders. Enter the command: pa stop all. 2. Go to the /opt/oa_infx_32lib/uninstall/uninstall_clientsdk folder and enter the following command:./uninstallclientsdk 3. In the About to uninstall page, press Enter to continue. 4. In the Uninstall Options page, the following options are available: Option 1 - Completely remove all features and components. Option 2 - Choose specific features that were installed by InstallAnywhere. 5. Type 1 and press Enter to completely remove all features and components. 6. After uninstallation of CMS, delete the /opt/oa_infx_32lib folder after the removal is complete. Installing and testing the Report client All workstations at which reports are viewed must have JRE and the Report client support files installed. After the installation of the files, you can run a test report to verify that the reports are working. Do not install the Report client on any system running Microsoft Windows Server 2008 R2 (Standard and Enterprise edition) or Microsoft Windows Server 2012 Standard edition. Do not install the Report client coresident on any IC servers. For different software requirements, running Basic Report along with other OA client applications is not supported. You can install the Report client on a Windows client workstation. This section includes the following topics: Installing the Report client support files for OA and earlier on page 154 Installation and Configuration February

154 Chapter 3: Installing Avaya OA components Running a test report on page 159 Installing the Report client support files for OA and later You must install the latest 32-bit version of JRE 1.8.0_xx. The other supporting files required for running the 3D reports are automatically downloaded by the OA Reporting applet when the report is accessed. From OA 7.3.4, the option for downloading the JRE and Reporting support files on the OA Reporting Web page using the Install Supporting Files link is removed. Installing the Report client support files for OA and earlier You must install the Report client support files for OA and earlier. To install JRE and the Report client: 1. Log in to a Windows client workstation with a user ID that has administrator privileges. 2. Open Microsoft Internet Explorer. 3. Do one of the following: If you have installed the Report subsystem on a Windows platform, enter: where report_server_fqdn is the fully qualified domain name of the Report server. You must specify the port number 8999 in reports URL as Avaya OA 7.3.x bypasses IIS for Windows. For Example, If you have installed the Report subsystem on a Solaris platform, enter: where report_server_fqdn is the fully qualified domain name of the Report server and port_number is the number the system assigns when you install the Report subsystem. The system uses port number 9080 for the Tomcat HTTP server on Solaris. 154 Installation and Configuration February 2017

155 Installing and testing the Report client If you have installed the Report subsystem on an AIX platform, enter: where report_server_fqdn is the fully qualified domain name of the Report server and port_number is the number the system assigns when you install the HTTP Server. The system usually uses port number 9080 or the alternative port number 9081 for the Tomcat HTTP server. For more information, see Avaya Operational Analyst Release 7.3.x Installation Planning and Prerequisites. A login screen displays. 4. Log in with the appropriate user ID and password of a user who belongs to the Avaya OA Report group. For more information, see Avaya Operational Analyst Release 7.3.x Installation Planning and Prerequisites. 5. Click Basic Reports to expand the report tree: Installation and Configuration February

156 Chapter 3: Installing Avaya OA components 6. Click Install Reporting Support Files. Installation instructions displays in the right pane. The following screen is for OA 7.3, 7.3.1, and 7.3.2: Following screen is for OA Follow the instructions displayed to: 156 Installation and Configuration February 2017

157 OA Release Basic Reports on Microsoft Windows 7 (64 bit) a. Check your Control Panel settings to see which version of JRE is on your computer.! CAUTION: CAUTION: If you have already installed JRE version 1.6.0_07, for example, you have already installed the Administration client on this computer, DO NOT REINSTALL JRE. If you reinstall JRE and the Administration client is on this computer, the Administration client policy information is deleted. Installing the JRE might adversely affect any applications currently using a different version of JRE. You might have to reinstall those applications that use a different version of JRE. b. Install JRE: a. For OA 7.3, 7.3.1, and install JRE version 1.6.0_07, if not already installed, using the link in the instructions that are displayed. b. For OA 7.3.3, install JRE version 1.6.0_45, if not already installed, using the link in the instructions that are displayed. c. Install the Report Client support files using the link in the instructions that are displayed. When the installation completes, the system displays the message Please close your browser when installation is complete. 8. Click Close to close the browser window to end the installation. 9. Continue with Running a test report on page 159. If you have any problems installing the Report client files, see Troubleshooting an installation on page 343 for help. For using higher version of JRE see Using latest version of Oracle JRE for Reporting Client for OA on page 349. OA Release Basic Reports on Microsoft Windows 7 (64 bit) If you are using Microsoft Windows 7 (64 bit) and Microsoft Internet Explorer 8 and have only the OA Reporting client installed on the system of the earlier Service Pack, then perform the following: 1. Upgrade to Microsoft Internet Explorer Uninstall the earlier/older Basic Reporting Client. Installation and Configuration February

158 Chapter 3: Installing Avaya OA components 3. Uninstall the older JRE 160_ Reinstall JRE 160_ Reinstall OA Reporting client support files. 6. Ensure you do not have any other OA applications running on the Windows 7 system. Configuring Microsoft Internet Explorer on Microsoft Windows 7 and 8.1 Adding OA Reporting Site URL to Compatibility View of Internet Explorer 1. Login to the Microsoft Windows system. 2. Open Microsoft Internet Explorer with administrative privileges (Run as administrator). 3. Open the OA Reporting Site URL. For example: 4. Add the above website to the Compatibility View settings of Internet Explorer. In Internet Explorer, click Settings > Compatibility View Settings > Add. OR In Internet Explorer, on the menu bar click Tools > Compatibility View Settings > Add. Adding OA Report URL to the trusted site list of Internet Explorer 1. Open Microsoft Internet Explorer. 2. Click Tools > Internet Options > Security > Trusted Sites > Sites > Add. When adding the OA Reporting URL to the trusted site uncheck Require server verification ( for all site in this zone option. Installing the reporting support files 1. Open the OA Report page. 2. Click Install Reporting Support files. 3. Click and install Oracle JRE 160_ Disable the auto JRE upgrade: a. Click Start > Control Panel > Java (32-bit). b. In the Java Control Panel window, click JRE Download > Never Auto Download. 158 Installation and Configuration February 2017

159 OA Release Basic Reports on Microsoft Windows 7 (64 bit) 5. After successful installation of Install Reporting Support files click Install the Report Client Support files and ensure that the VRPT file is downloaded and installation is completed. 6. After successful installation of VRPT files close and restart the Internet Explorer browser. Verifying the installation of Reporting files 1. Click Start > Control Panel. 2. In the Control Panel window, click Program and Features. 3. In the Program and Features window verify that Basic Reporting Client is available in the list of installed programs. Running a test report If you have problems running a test report, see Avaya Operational Analyst Release 7.3.x Installation Planning and Prerequisites. To run a test report: 1. Log in to the client workstation with a user ID that has reporting privileges. 2. Open Microsoft Internet Explorer. 3. Do one of the following: If you have installed the Report subsystem on a Windows platform, enter: where report_server_fqdn is the fully qualified domain name of the server where you install the Report subsystem. You must specify the port number 8999 in reports URL as Avaya OA 7.3.x bypasses IIS for Windows. For Example, If you have installed the Report subsystem on a Solaris platform, enter: where report_server_fqdn is the fully qualified domain name of the Report server and port_number is the number the system assigns when you install the Report subsystem. The default port number for the Tomcat server is 9080 for Solaris. The system does not assign port number during installation. Installation and Configuration February

160 Chapter 3: Installing Avaya OA components If you have installed the Report subsystem on an AIX platform, enter: where report_server_fqdn is the fully qualified domain name of the Report server and port_number is the number the system assigns when you install the HTTP Server. The default port number for the Tomcat server is 9080 for Solaris. The system does not assign port number during installation. For more information, see Avaya Operational Analyst Release 7.3.x Installation Planning and Prerequisites. A login screen displays. 4. Log in with the appropriate user ID and password of a user who belongs to the Avaya OA Report group. For more information, see Avaya Operational Analyst Release 7.3.x Installation Planning and Prerequisites. 5. Click Basic Reports to expand the report tree: 6. Expand the report folders in the left pane and then run a test report. Completing the installation This section includes the following topics: Setting up remote access on page Installation and Configuration February 2017

161 Completing the installation Configuring the NumDSWorkerThreads parameter on the Report servers on page 161 Configuring the SMPOptLevel parameter on the TimesTen server on page 163 Configuring Cognos for multibyte language support on page 164 The detail Impromptu reports under the Impromptu\oadb folder, ContactsBy*Site.imr and ContactsBy*Media.imr are unavailable with this configuration. on page 165 The detail Impromptu reports under the Impromptu\oadb folder, ContactsBy*Site.imr and ContactsBy*Media.imr are unavailable with this configuration. on page 165 Setting up remote access For server systems that require remote troubleshooting by Avaya, at least one Avaya system in the customer network must be equipped for remote access. The details of what this includes depends on the agreement with the customer. Contact Avaya for more information. Configuring the NumDSWorkerThreads parameter on the Report servers You must configure the NumDSWorkerThreads parameter for every server where you install the Report subsystem. This parameter affects the performance of the system. To set the NumDSWorkerThreads parameter perform the following: 1. Open a command prompt window. 2. Open the following file in a text editor: %PABASE%\Stumbras\webapp\WEB-INF\config\RTPAService\ RTPAService.properties (Windows) $PABASE /strumbas/tomcat/webapps/root/web-inf/config/ RTPAService/RTPAService.properties (Solaris) $PABASE/strumbas/tomcat/webapps/ROOT/WEB-INF/config/ RTPAService/RTPAService.properties (AIX) Installation and Configuration February

162 Chapter 3: Installing Avaya OA components 3. Search for the NumDSWorkerThreads parameter. See the following file for an example: # #- RTPAService.properties #- #- This is a configuration file that contains properties that are independent #- of the OA Admin Mgr provided properties. #- #- The content of RTPAService.properties will not require any localization. # # Number of DataSet event processing worker threads. Should be set to the # number of CPUs on the reporting server host platform. # NumDSWorkerThreads = 1 4. Change the value to equal the number of CPUs on the server. For example, if the Report server has 4 CPUs, enter Save and close the file. 6. Restart Stumbras on each Report server. For Windows: 1. Select Start > Programs > Administrative Tools > Services. The Services dialog box displays. 2. Highlight the Stumbras service and restart it. For Solaris: 1. Open a command prompt window. 2. Enter the following commands:. /opt/bi/.profile cd /opt/bi/stumbras/tomcat/bin For OA and earlier:./shutdown.sh./startup.sh For OA and later:./stopoareport.sh./startoareport.sh For AIX: 1. Open a command prompt window. 162 Installation and Configuration February 2017

163 Completing the installation 2. Enter the following commands:. /opt/bi/.profile cd /opt/bi/stumbras/tomcat/bin./shutdown.sh./startup.sh Configuring the SMPOptLevel parameter on the TimesTen server The SMP Optimization Level (SMPOptLevel) parameter for TimesTen can be set on the server where you install the Real-time subsystem. The procedure for setting this parameter differs for Windows, Solaris, and AIX. Windows setup: To set the SMPOptLevel parameter: On Windows Server 2008 R2 and Microsoft Windows Server 2012 Standard edition, the following steps opens the 64-bit ODBC interface. However, to open the 32-bit ODBC interface, see For 32-bit ODBC interface: on page 163. For 64-bit ODBC interface: 1. Select Start > Settings > Control Panel. The system displays Control Panel window. 2. Select Administrative Tools. The system displays the Administrative Tools window. 3. Select Data Sources (ODBC). The system displays the ODBC Data Source Administrator window. 4. Under the System DSN tab, select dss Click Configure. 6. Select the First Connection tab. 7. Under the SMP Optimization Level, enter 0 if the server has one CPU, or enter 1 if the server has two or more CPUs. 8. Click OK three times so save the setting. For 32-bit ODBC interface: 1. Select Start > Run. The system displays the Run dialog box. 2. In the text field, type C:\Windows\SysWOW64\odbcad32 and click OK. The system displays the 32-bit ODBC client interface. Installation and Configuration February

164 Chapter 3: Installing Avaya OA components 3. Under the System DSN tab, select dss Click Configure. 5. Select the First Connection tab. 6. Under the SMP Optimization Level, enter 0 if the server has one CPU, or enter 1 if the server has two or more CPUs. 7. Click OK three times so save the setting. Solaris and AIX setup: To set the SMPOptLevel parameter: 1. Open a command prompt window. 2. Enter: vi /var/timesten/sys.odbc.ini 3. Search for the SMPOptLevel parameter. 4. Change the value to 0 if the server has one CPU, or change it to 1 if the server has two or more CPUs. 5. Press Esc. 6. Enter: :wq! This writes and quits the file. Configuring Cognos for multibyte language support If you install the Advanced Reporting subsystem and the customer has installed Cognos Impromptu Administrator Version 6.2 multibyte English to support Japanese and other multibyte languages, you must rename two program folders. If you are not using Cognos Impromptu Administrator Version 6.2, you can skip this procedure. The system creates the following extra folders: cubes_intl Impromptu_intl These folders must be renamed so that correct programs are used by the Advanced Reporting subsystem. To rename the folders: 1. Open Windows Explorer. 164 Installation and Configuration February 2017

165 Completing the installation 2. Navigate to c:\program Files\Avaya\BI\reports\cognos folder for 32-bit system and the c:\program Files (X86)\Avaya\BI\reports\cognos folder for 64-bit system. 3. Rename the folder cubes to cubes_ver7. 4. Rename the folder cubes_intl to cubes. 5. Rename the folder Impromptu to Impromptu_ver7. 6. Rename the folder Impromptu_intl to Impromptu. The detail Impromptu reports under the Impromptu\oadb folder, ContactsBy*Site.imr and ContactsBy*Media.imr are unavailable with this configuration. Installation and Configuration February

166 Chapter 3: Installing Avaya OA components 166 Installation and Configuration February 2017

167 Chapter 4: Configuring Avaya OA subsystems and event collectors This section describes how to configure the various subsystems, client software, and data collection software of Avaya OA. You can use the Avaya OA Administration client to configure the Avaya OA software to perform data collection and reporting. Before you can configure the Event Collector server for Avaya IC, you must perform the following: Administer the Real-time subsystem. Create a corresponding IC source subsystem in Avaya OA. If your installation includes CMS, whether it includes Avaya IC, you must add CMS and ACD source subsystems. When configuring Avaya OA subsystems, follow the correct order in which you start the Avaya OA processes. This order avoids Stumbras web application exceptions. To start the Avaya OA processes perform the following: 1. After you install Avaya OA, ensure that you stop Stumbras. 2. Start the Core Avaya OA servers, if the servers are not running. Use the following command to start the Avaya OA servers: pa start all 3. Configure the required Avaya OA servers through the Admin client. 4. Ensure that the Avaya OA servers are running. 5. Start the Stumbras server. Following is the correct order in which you stop the Avaya OA processes to avoid Stumbras web application exceptions. 1. Stop the Stumbras server. 2. Stop the Avaya OA servers. Use the following command to stop the Avaya OA servers. pa stop all If you are using Avaya OA with CMS, but without IC, the RealTime / DataManager server is nonexistent as part of the OA server system. You must delete the RTPAService that retrieves real time data to prevent RTPAService specific errors. 1. Go to the Stumbras admin at 2. Click the Startup Admin link. Installation and Configuration February

168 Chapter 4: Configuring Avaya OA subsystems and event collectors 3. Select the com.avaya.stumbras.services.rtpa.rtpaservice check box. 4. Click Delete. 5. Restart the Stumbras service. Do not view the real time reports, the IC specific Tabular and the Basic reports, as the RealTime / DataManager server is nonexistent as part of the OA server system. This section includes the following topics: Administration client options on page 168 Starting the Avaya OA Administration client on page 172 Adding a Real-time subsystem on page 173 Adding an Avaya IC Source subsystem on page 176 Adding a CMS subsystem on page 177 Adding an ACD Source subsystem on page 179 Adding a Report subsystem on page 181 Administering the Source-EC (Event Collector) server on page 183 Administering the Source-EC Bridge (Event Collector Bridge) on page 191 Completing initial administration on page 195 Configuring SSL for OA on page 196 Changing the port number of the Tomcat server on page 205 For more information, see the Administration Client Help. Administration client options Before you configure subsystems and the event collectors, you might set options on the Administration client. During OA Admin Client launch, the browser would display JRE upgrade dialog box. You must not upgrade the JRE. This section includes the following topics: Customizing the Administration client on page 169 Setting the archive time zone definition on page Installation and Configuration February 2017

169 Administration client options Customizing the Administration client The Administration client installation process creates two HTML files in the %PABASE% folder, AdminPol.html and AdminSig.html. To run the Administration client, you use one of these HTML files. To use the Java policy file security model, use AdminPol.html. To use the signed jar file security model, use AdminSig.html. From OA onwards the new OA Adminclient will be used as a OOTB client. The desktop s adminclient shortcut will launch the new OA Adminclient. To run the old old adminclient open the html file from the following location: %PABASE%\BI\AdminSig.html Both HTML files include applet parameters that you can be customize. All applet parameters are set to a default value at the time of installation. Usually you do not have to change these parameters.! CAUTION: CAUTION: You must take care when changing these values as it can cause the HTML file to become corrupted and you unable to run the Administration client. Before editing either of the files, make a backup version of the original files (for example, AdminPol.html.orig and AdminSig.html.orig). Lines in the HTML file that specify the value of an applet parameter have the following format: <PARAM NAME="name" VALUE="value"> The applet parameters that you can customize include the following: Parameter name SERVER_NAME Value Host name for Historical server to which the client connects to. Set this host name to the Historical server specified during installation. Installation and Configuration February

170 Chapter 4: Configuring Avaya OA subsystems and event collectors Parameter name Value LOCALE FONT Set to the locale of the language selected during install. zh_cn - Chinese (Simplified) zh_tw - Chinese (Traditional) en_us - English (US) [default value] fr_fr - French (Parisian) de_de - German (Traditional) hu_hu - Hungarian it_it - Italian ja_jp - Japanese ko_kr - Korean (South Korea) pt_br - Portuguese (Brazilian) re_ru - Russian es_co - Spanish (Colombian) th_th - Thai Arial Unicode MS (default value) Thai requires the Tahoma font. TRACE_LEVEL Logging trace level: 10, 20, or 30. CORBA_TRACE DAYLIGHT_APPLIES DAYLIGHT_START DAYLGIHT_END DAYLIGHT_CLOCK_CHANGE Turns on/off Corba trace ability (yes/no). Set to yes only when custom daylight-saving settings are needed. Set to start date only when custom daylight-saving settings are needed. Set to end date only when custom daylight-saving settings are needed. Clock offset, only when custom daylight-saving settings are needed. Changing fonts: By default the Arial Unicode MS font is used for the FONT parameter. This font can display the characters in any language except Thai, which requires the Tahoma font. The associated TTF file (ARIALUNI.TTF by default) is installed into the %windir%\fonts folder. When you remove the administration client, this font is not removed. This is done to prevent removing a file that existed before the installation of the Avaya OA. You can set the FONT parameter to any other valid, installed font. For example, to better display simplified Chinese, someone might use the SimSun font. If the OS has that font, you can change the FONT applet parameter to use the font. For most installations, the default font is adequate and you do not have to change this parameter. 170 Installation and Configuration February 2017

171 Administration client options To display Thai, you must install the Tahoma font and change the FONT parameter to Tahoma. Administering multiple Avaya OA sites: You install the Administration client on Windows systems that are usually separate from the Avaya OA servers. You can use one Administration client to administer multiple, independent Avaya OA installations. To set this up for multiple Avaya OA installations, the HTML files that are used to launch it are set at installation with the name of the Historical server to which the client connects to. If you have to access multiple OA servers from a single Administration client install, you must edit the appropriate HTML file to point the client to the Historical server for each OA install. If you are using signed jar files, edit the %PABASE%\AdminSig.html file. If you are using java policy files, edit the %PABASE%\ AdminPol.html file. By default, the system uses java policy files. In either case, you must change following line in the HTML file: <PARAM NAME="SERVER_NAME" VALUE=xxxxx> Replace xxxxx with the fully qualified domain name for the Historical server of the OA to be administered from this client. The next time the Administration client runs, the client connects to the new Historical server. This file is on the client system. For more information, see Avaya Operational Analyst Release 7.3.x Installation Planning and Prerequisites. Setting the archive time zone definition Most time zones have more than one time zone definition. For example, GMT+8 has 14 different definitions, including Australia/Perth and Asia/Singapore. When an upgrade to OA 7.0 happens, the system uses default time zones. By default, the Administration client defaults to Australia/Perth if the corresponding start of day equates to midnight GMT+8. To change the archive time zone definition: 1. Open the Administration client. For more information, see Starting the Avaya OA Administration client on page Select Container Archives. The Container Archives screen displays in the right pane. 3. Under Archive Time Zone, if the selected time zone definition does not match Local (Client) time zone, select the proper time zone definition. For example, if definition is the default of Australia/Perth and you are in Singapore, select Asia/Singapore. 4. Click Save. Installation and Configuration February

172 Chapter 4: Configuring Avaya OA subsystems and event collectors Starting the Avaya OA Administration client To run OA Administration client perform the following: 1. Go to the folder where you install the Administration client is. 2. Double-click the AdminPol.html file. The Administration Login dialog box displays. 3. Enter the user ID and password. 4. Click OK. The OA Welcome dialog box displays for a few seconds then the Administration Client screen displays. 5. Administer the appropriate subsystems: Adding a Real-time subsystem on page 173 Adding an Avaya IC Source subsystem on page Installation and Configuration February 2017

173 Adding a Real-time subsystem Adding a CMS subsystem on page 177 Adding an ACD Source subsystem on page 179 Adding a Report subsystem on page 181 Administering the Source-EC (Event Collector) server on page 183 Administering the Source-EC Bridge (Event Collector Bridge) on page 191 The system adds the Historical subsystem automatically when installing OA. Adding a Real-time subsystem To add a Real-time subsystem: 1. In the OA Administration tree, select Subsystems. The Subsystems administration screen displays in the right pane. 2. Click Add. The Add Subsystem screen displays. Installation and Configuration February

174 Chapter 4: Configuring Avaya OA subsystems and event collectors 3. Select the Real-time option under Type. The Add Subsystem screen displays showing the fields required to add a Real-time subsystem. 4. Enter the Name of the server where you install the Real-time subsystem. 5. Enter the Location of the server where you install the Real-time subsystem. You can enter the Internet domain name, the fully qualified domain name, or the IP address of the server. Depending on what you enter, one of the following occurs: If you enter a domain name and the IP address is using DNS or entries in a hosts file, go to the next step. If you enter a domain name and the system cannot determine the IP address using DNS or entries in a hosts file, you cannot go to the next step. Until you fix the DNS administration or update the hosts file you cannot go to the next step. If you enter an IP address and the system finds the associated domain name, you can go to the next step. 174 Installation and Configuration February 2017

175 Adding a Real-time subsystem If you enter an IP address and the system cannot determine the associated domain name using DNS or entries in a hosts file, the following message displays: The Internet domain name associated with the IP address could not be found. Do you wish to continue using the specified IP address? You can go to the next step, but you must fix the DNS administration or update the hosts file. 6. Click OK. The following shows the new subsystem added to the table in the Subsystems screen: 7. Click Save. The request is submitted to the server where you install the Historical subsystem. Installation and Configuration February

176 Chapter 4: Configuring Avaya OA subsystems and event collectors Adding an Avaya IC Source subsystem You add an Avaya IC Source subsystem for each Event Collector to associate it with a Real-time subsystem. To add an Avaya IC Source subsystem perform the following: 1. In the OA Administration tree, select Subsystems. The Subsystems administration screen displays in the right pane. 2. Click Add. The Add Subsystem screen displays. 3. Select the Source option under Type. 4. Select Avaya Interaction Center from the Source Type drop-down list. The Add Subsystem screen displays showing the options for an IC Source subsystem. 176 Installation and Configuration February 2017

177 Adding a CMS subsystem 5. Select Automatic generation to have the OA generate a Source ID. You need this Source ID to configure the Event Collector server. For more information, see Administering the Source-EC (Event Collector) server on page In Name, enter a unique subsystem name. Select a name that indicates which Real-time subsystem this Avaya IC source subsystem is associated with. This association helps reduce confusion if your installation contains several Real-time subsystems and several Avaya IC source subsystems. 7. Select the name of the Real-time subsystem to which to send the data. 8. Select the check box next to the appropriate Historical Store and select the appropriate Historical subsystem. 9. Click OK. The system adds the new subsystem to the table in the Subsystems screen. 10. Click Save. The request is submitted to the server where you install the Historical subsystem. 11. Repeat this procedure for each Event Collector and Real-time subsystem pair. Adding a CMS subsystem To add a CMS subsystem: 1. In the OA Administration tree, select Subsystems. The Subsystems administration screen displays in the right pane. 2. Click Add. The Add Subsystem screen displays. Installation and Configuration February

178 Chapter 4: Configuring Avaya OA subsystems and event collectors 3. Select the CMS option under Type. The Add Subsystem screen displays showing the options for a CMS subsystem. 4. Enter the Name of the CMS server. 5. Enter the Location of the CMS server. You can enter the Internet domain name, the fully qualified domain name, or the IP address of the server. Depending on what you enter, one of the following occurs: If you enter a domain name and the IP address is using DNS or entries in a hosts file, you can go to the next step. If you enter a domain name and the system cannot determine the IP address using DNS or entries in a hosts file, you cannot go to the next step. Until you fix the DNS administration or update the hosts file you cannot go to the next step. If you enter an IP address and the system finds the associated domain name, you can go to the next step. 178 Installation and Configuration February 2017

179 Adding an ACD Source subsystem If you enter an IP address and the system cannot determine the associated domain name using DNS or entries in a hosts file, the following message displays: The Internet domain name associated with the IP address could not be found. Do you wish to continue using the specified IP address? You can go to the next step, but you must fix the DNS administration or update the hosts file. 6. Click OK. The system adds the new subsystem to the table in the Subsystems screen. 7. Click Save. The request is submitted to the server where you install the Historical subsystem. Adding an ACD Source subsystem To start the flow of ACD data, you must first create a CMS subsystem, then add an ACD Source subsystem to link them together. 1. In the OA Administration tree, select Subsystems. The Subsystems Administration screen displays in the right pane. 2. Click Add. The Add Subsystem screen displays. 3. Select the Source option under Type. Installation and Configuration February

180 Chapter 4: Configuring Avaya OA subsystems and event collectors 4. Select ACD from the Source Type drop-down list. The Add Subsystem screen displays showing the options for an ACD subsystem. 5. Leave the Source ID Automatic generation option selected. 6. Enter a name for the subsystem. 7. Select the associated CMS subsystem from the CMS subsystem drop-down list. 8. Enter the ACD number (1-8) for this ACD. This number must correspond to an ACD number administered on the CMS server. 9. Select the types of data that should be kept in the Historical subsystem. 10. Enter a name for the static data collection job that is to be created. 11. Click OK. The system adds the new subsystem to the table in the Subsystems screen. You add up to eight ACDs for each CMS. The OA can handle up to 30 CMS servers, for a total of 240 ACDs. 180 Installation and Configuration February 2017

181 Adding a Report subsystem 12. Click Save. The request is submitted to the server where you install the Historical subsystem. Adding a Report subsystem To generate reports about the data you have collected, you must add a Report subsystem: 1. In the OA Administration tree, select Subsystems. The Subsystems administration screen displays in the right pane. 2. Click Add. The Add Subsystem screen displays. 3. Select the Report option under Type. The Add Subsystem screen displays with the options for the Report subsystem. Installation and Configuration February

182 Chapter 4: Configuring Avaya OA subsystems and event collectors 4. Enter the Name of the server where you install the Report subsystem. 5. Enter the Location of the server where you install the Report subsystem. You can enter the Internet domain name, the fully qualified domain name, or the IP address of the server. Depending on what you enter, one of the following occurs: If you enter a domain name and the IP address is using DNS or entries in a hosts file, you can go to the next step. If you enter a domain name and the system cannot determine the IP address using DNS or entries in a hosts file, you cannot go to the next step. Until you have fix the DNS administration or update the hosts file you cannot go to the next step. If you enter an IP address and the system finds the associated domain name, you can go to the next step. If you enter an IP address and the system cannot determine the associated domain name using DNS or entries in a hosts file, the following message displays: The Internet domain name associated with the IP address could not be found. Do you wish to continue using the specified IP address? You can go to the next step, but you must fix the DNS administration or update the hosts file. 6. Click OK. The system adds the new subsystem to the table in the Subsystems screen. 7. Click Save. The request is submitted to the server where you install the Historical subsystem is installed. 8. Restart the Report subsystem on the server where you install the Report subsystem. Perform one of the following: For Windows: 1. Log in using the appropriate user ID and password. For more information, see Avaya Operational Analyst Release 7.3.x Installation Planning and Prerequisites. 2. Select Start > Programs > Administrative Tools > Services. 3. Stop and Start the Tomcat service. For OA and earlier: Stop and Start the Stumbras-Tomcat service. For OA and later: Stop and Start the Avaya OA Reporting Application service. For Solaris or AIX: 182 Installation and Configuration February 2017

183 Administering the Source-EC (Event Collector) server 1. Log in using the appropriate user ID and password. For more information, see Avaya Operational Analyst Release 7.3.x Installation Planning and Prerequisites. 2. Open a command prompt window. 3. Enter the following commands:. /opt/bi/.profile cd /opt/bi/stumbras/tomcat/bin For OA and earlier:./shutdown.sh./startup.sh For OA and later:./stopoareport.sh./startoareport.sh Administering the Source-EC (Event Collector) server After you have created an Avaya IC Source subsystem, you must configure the Source-EC (Event Collector) server. The Event Collector server collects many types of data from ADU servers, including agent data, queue data, service class data, and outbound job statistics. There is a one-to-one relationship between each Event Collector server and the associated OA Real-time subsystem to which it sends data. If you have more than one Real-time subsystem, you need more than one Event Collector server. Before you administer an Event Collector server, you must know the following information: The Real-time System ID (Source ID) of the OA Real-time subsystem that receives data from the Event Collector server. The host system name or IP address of the server where you install the Real-time subsystem that receives data from the Event Collector server. For more information, see Adding a Real-time subsystem on page 173. Which Avaya IC domains the Event Collector server monitors for agent ADU data. The list of monitored domains for an Event Collector server must include all domains at the site that contain agents and all domains containing ADU servers that monitor agents at the site. Which Event Collector server monitors service class detail data for web channels, for example, chat, and . Installation and Configuration February

184 Chapter 4: Configuring Avaya OA subsystems and event collectors For OA Reports to reflect proper Agent State, Service class, and Queue data ensure that you configure the Event Collector to receive ADU event streams and the blender information from Interaction Center. The domains to monitor are Voice Web and Agent domains. These domains include: The channel connector ADU from the TS and WACD. Blender events in Agent domains that have Blender and Blender Workflow. These domains are required for: Channel task load IC desktop crash Logout events Failover In site administration of Voice domains, you can only have one EC for each particular site and one TSQS for each site administered to provided necessary blender queue statistic of VDNs. Any other configuration results in extraneous and duplicate events streams that cause inaccurate display of data in OA TRW and Basic Reports. The system globally updates the Advocate ADU business objects, for example, Serviceclasssummary, serviceclassstate, and serviceclassdetail, throughout all ADUs. These objects are filtered by EC with the LRMIDs associated with TSA (voice) and WAA ( and chat). You can only have one EC for each LRMID. This section includes the following topics: Determining Real-time System ID and Data Manager Host on page 184 Administering the Event Collector server on page 185 Determining Real-time System ID and Data Manager Host The Real-time System ID and Data Manager Host values are required to administer the Event Collector Server. You input these values on the Event Collector tab of the Event Collector Server Editor window in Steps 18 and 19 of Administering the Source-EC (Event Collector) server on page 183. Follow these steps to determine the values of Real-time System ID and Data Manager Host from the Subsystems window of the OA Administration client: 1. On the Subsystems window, find the Real-time subsystem that is communicating with this Event Collector instance. Its row displays the host name and IP address information in the appropriate columns of the table. 2. Select the Avaya IC data source associated with the selected Real-time subsystem. 184 Installation and Configuration February 2017

185 Administering the Source-EC (Event Collector) server If you do not know the subsystem name of the Avaya IC data source, you can select several data sources until you find the correct one. 3. Press Modify. 4. The Modify Subsystem dialog box displays. 5. Verify the Real-time subsystem field matches the Real-time subsystem you selected in Step The Real-time System ID value displays in the Source ID field. Administering the Event Collector server To administer the Event Collector Server: 1. In the IC Manager administration window, select the Server tab. The Server tab displays information on each server. Installation and Configuration February

186 Chapter 4: Configuring Avaya OA subsystems and event collectors 2. Select Server > New... The Select or enter server type dialog box displays. 3. Select EventCollector from the Server Type list and click Ok. The Server Editor dialog box displays. 4. Enter the name of the Event Collector server in the Name field. Select a meaningful name. If you define multiple Event Collector servers, use a unique name for each Event Collector server. 5. Select the IP address where the Event Collector server runs from the Host drop-down box. Ensure the Event Collector server runs on the same host as the agent ADU servers that it monitors. 186 Installation and Configuration February 2017

187 Administering the Source-EC (Event Collector) server Important: 6. Accept the default Port number. 7. Select the Avaya IC Domain within which this instance runs. For more information, see Avaya Interaction Center Release 7.3.x Installation Planning and Prerequisites. 8. Accept the default folder where Avaya IC runs. This folder is: For Windows, %AVAYA_IC73_HOME%\etc For Solaris and AIX, $AVAYA_IC73_HOME/etc 9. Accept the path and file name in the Executable field: For Windows, %AVAYA_IC73_HOME%\bin\ECServer For Solaris and AIX, $AVAYA_IC73_HOME/bin/ECServer 10. Select Auto Start. Clear Use UTC and Security.! Important: After configuring the Event Collector server, verify that you configure all ADU and Directory servers (DS) to use GMT. 11. Select the Event Collector tab. 12. Select the site associated with this instance of Event Collector server from the Site drop-down list. This value must always match the site configured for the Telephony Queue Statistics servers from which the Event Collector server collects Telephony Server Queue statistics. Installation and Configuration February

188 Chapter 4: Configuring Avaya OA subsystems and event collectors 13. Choose the domains that the Event Collector server monitors by clicking on the ellipses ( ) after the Domains to Monitor field. The Domains to Monitor dialog box displays. 14. To add a domain, select >= in the dialog box. The Domains to Monitor dialog box displays with a drop-down list. 188 Installation and Configuration February 2017

189 Administering the Source-EC (Event Collector) server 15. Click the Domains drop-down list. A list of domains displays. 16. Click the domain you want to add. Repeat the same process for each domain you want to add. The list of monitored domains for an Event Collector server must include all domains at the site that contain agents and all domains containing ADU servers that monitor agents at the site. For example, if the agents at site taos are configured to be in domains taos_user1 and taos_user2, and the ADU servers monitoring those agents are in domains taos_voice1 and taos_voice2, then the Event Collector for site taos must be configured to monitor domains taos_user1, taos_user2, taos_voice1, and taos_voice2. The order that the domains are listed does not matter. Installation and Configuration February

190 Chapter 4: Configuring Avaya OA subsystems and event collectors 17. When you finish adding domains, select Ok. The EventCollector tab displays. CAUTION:! CAUTION: If the configuration has two Event Collector servers, do not use the same value when administering the Real-time System ID and the Data Manager Host in the next two steps. If you assign the same value, the connection to the servers does not stay active. 18. Enter the Real-time System ID associated with the real time system that is to receive data from this Event Collector server instance. Real-time System IDs are numeric values that a system administrator assigns and associates with an OA Real-time subsystem during OA subsystem administration. The Real-time System ID must match the Source ID configured for the OA Real-time system. For more information, see Determining Real-time System ID and Data Manager Host on page Enter the Data Manager Host for this Event Collector server instance. This is the name or IP address of the server hosting the OA Real-time subsystem that is to receive data from this Event Collector server instance. The OA Real-time subsystem can be co-located on the same system as the Event Collector server. If so, use the name or IP address of the system hosting both Avaya IC and the OA Real-time subsystem. 20. Configure the Agent Availability Algorithm as follows: Inbound Availability: If advocateflag=1 for an agent, OA applies the agent load based algorithm in determining agent availability. Otherwise OA uses the agent or channel-based availability algorithm as specified by the EC configuration. Agent load based: If the summation of media.contactcount is less than load, set availability to available. Otherwise, set availability to unavailable. 190 Installation and Configuration February 2017

191 Administering the Source-EC Bridge (Event Collector Bridge) Channel load based: If the summation of media.contactcount is less than the summation of media.load, set availability to available. Otherwise, set availability to unavailable. These configuration options indicate that if the agent is an Advocate agent, the system automatically uses agent load based algorithm. If the agent is non-advocate, the system uses the algorithm based on the setting chosen during the EC configuration in IC Manager. 21. The Monitor WAA field specifies whether this EC instance listens to service class details for web channels, for example, chat, and . The default value is No. Only one EC server in an installation can monitor the WAA. Avaya recommends that the EC instance at the same site as the WAA, monitor the WAA. 22. Select the Debug tab. 23. Click the ellipses ( ) next to Trace levels. 24. In the Trace Levels dialog box, set the fields as shown in the following table: Field idl flush usr5 Clear this option. Clear this option. Recommended entry Select this option. This causes the Event Collector server to log messages to the trace file. This trace file might assist in troubleshooting problems. 25. Click Ok. For more information, see Avaya IC Administration Volume 1: Servers and Domains. 26. Click Ok to complete the Event Collector server administration. For more troubleshooting information see Avaya Operational Analyst Release 7.3.x Maintenance and Troubleshooting Guide. Administering the Source-EC Bridge (Event Collector Bridge) If you have installed Business Advocate, you must configure the Source-Event Collector Bridge (EC Bridge). The EC Bridge functions as a gateway between the EC and Avaya Business Advocate. The EC Bridge queries Business Advocate data and collects Business Advocate administration events that are published to Microsoft Message Queuing (MSMQ) by Business Advocate. The system sends this data to the EC which in turn forwards the data to the OA Real-time subsystem. This data supports OA real-time and historical reporting requirements. Installation and Configuration February

192 Chapter 4: Configuring Avaya OA subsystems and event collectors Advocate ODBC data source must exist on the servers where you install the standby ECB. Before you administer an EC Bridge, you must know the system name of the primary Business Advocate Avaya IC subsystem. If you install only one Business Advocate subsystem, that subsystem is the primary Business Advocate subsystem. If you install multiple Business Advocate subsystems, the first subsystem you install is the primary Business Advocate subsystem. The system name of the primary Business Advocate system is a system name and not an IP address. This is the name of the system as it is known by the MSMQ subsystem. To administer the EC Bridge perform the following: 1. In the IC Manager administration window, select the Server tab. The Server tab displays information on each server. 192 Installation and Configuration February 2017

193 Administering the Source-EC Bridge (Event Collector Bridge) 2. Select Server > New... The Select or enter server type dialog box displays. 3. Select ECB from the Server Type list and click Ok. The Server Editor dialog box displays. 4. Enter the name of the EC Bridge in the Name field. Select a meaningful name. If you are defining multiple EC Bridges, use a unique name for each. 5. Select the IP address where the EC Bridge runs from the Host drop-down box. The EC Bridge must run on the same host where you install Business Advocate. Installation and Configuration February

194 Chapter 4: Configuring Avaya OA subsystems and event collectors 6. Accept the default Port number. 7. Select the Avaya IC Domain in which this instance runs. This domain is to be the same domain as the Business Advocate Resource Manager. The Business Advocate Resource Manager is on the same system as the EC Bridge. For more information, see Avaya Interaction Center Release 7.3.x Installation Planning and Prerequisites. 8. Accept the default folder where Avaya IC runs. This folder is to be %AVAYA_IC73_HOME%\etc. 9. Accept the path and the file name in the Executable field, %AVAYA_IC73_HOME%\bin\ ECServer. 10. Select Auto Start. Clear Use UTC and Security. 11. Select the Event Collector Bridge tab. 12. Specify the name of the primary Business Advocate host system. This name is the host name as known to the MSMQ subsystem for the first (or only) installed Business Advocate subsystem.! Important: Do not use an IP address for the Business Advocate host name. 13. Select the Debug tab. 14. Click the ellipses ( ) next to Trace levels. Important: 194 Installation and Configuration February 2017

195 Completing initial administration 15. In the Trace Levels dialog box, set the fields as shown in the following table: Field idl flush usr5 Clear this option. Clear this option. Recommended entry Select this option. This causes the Event Collector server to log messages to the trace file. This trace file might assist in troubleshooting problems. 16. Click Ok. For more information, see Avaya IC Administration Volume 1: Servers and Domains. 17. Click Ok to complete the Event Collector Bridge administration. For more troubleshooting information see Avaya Operational Analyst Release 7.3.x Maintenance and Troubleshooting Guide. Completing initial administration You can use the OA Administration client to administer certain tasks, but this document does not cover. These tasks include: Activating the remaining subsystems and the interface services. Defining daily intervals. Configuring data collection properties. Setting data retention time (Max Capacity). Designing data containers. Aggregating and archiving data. Purging data. Maintaining data consistency. Activating appropriate CMS Aux Reason Code columns. For more information, see Administration Client Help. Your Avaya planning and installation support representative or your Avaya Business Partner can provide support with these database administration tasks. Installation and Configuration February

196 Chapter 4: Configuring Avaya OA subsystems and event collectors Configuring SSL for OA Avaya OA 7.3.x supports SSL functionality. However, SSL functionality is OPTIONAL and you must configure SSL manually for OA. By default you install OA on a non secured port (Http). When you configure SSL for OA, the OA Stumbras reporting server receives data on a secured port (https). You can configure Stumbras in the following three ways: Only Secure Mode (SSL). Only Unsecure Mode (No SSL) By default you configure the Stumbras on Unsecured Mode (No SSL). You must configure SSL on OA for the Stumbras reporting server to receive data on a secured port (https). For configuring SSL, a web server must have an associated Certificate for each external interface (IP address) that accepts secure connections. Configure a secure port on the web server to make use of the previous created certificate. For accessing Reporting Client on the Microsoft Internet Explorer, enable the following security options in the Advanced tab of Internet Options: Select the Use SSL 3.0 check box. Select the Use TLS 1.0 check box. When you first access the reports over https protocol, you must trust the server certificates before proceeding further. The Data Export Client being a non browser client requires a different way to import and trust the server certificates. A new utility called SunInstallCert is provided to import the server certificates in the client trust store. For more information, see the Avaya Operational Analyst Release 7.3.x Data API Utility Guide. This document contains information about self signed certificates. For more information, see to the documentation for respective web servers. Configuring SSL for Windows for OA and earlier Perform the following steps for configuring SSL for Windows: Generate the KeyStore file on page Installation and Configuration February 2017

197 Configuring SSL for OA Configure Tomcat for using the Keystore file on page 197 Configure OA to work with SSL on page 198 Generate the KeyStore file 1. Open command prompt type: cd %JAVA_HOME%/bin Run the keytool command: keytool -genkey -alias tomcat -keyalg RSA This command creates a new file in the home folder of the user under which you run it, named.keystore. To specify a different location or a file name, add the -keystore parameter, followed by the complete path to your keystore files as the following shows: keytool -genkey -alias tomcat -keyalg RSA \ -keystore \path\to\my\keystore 2. After running this command, you are prompted for the keystore password. The default password used by Tomcat is changeit. You can specify a custom password in the server.xml configuration file. 3. Answer all questions in the questionnaire. 4. Put the.keystore file in the webapp folder of OA. By default the.keystore file is in C:\Documents and Settings\ <username>\. Configure Tomcat for using the Keystore file 1. Open the server.xml file located at %PABASE%\stumbras\tomcat\conf directory. 2. Find the Connector element tag that has attribute port=8999 and comment it. <!--Connector port="8999" protocol="http/1.1" /--> 3. Add a new Connector element that replaces the above HTTP based connector element as follows: Installation and Configuration February

198 Chapter 4: Configuring Avaya OA subsystems and event collectors <Connector classname="org.apache.tomcat.service.pooltcpconnector"> <Parameter name="handler" value="org.apache.tomcat.service.http.httpconnectionhandler"/> <Parameter name="port" value="8443"/> <Parameter name="socketfactory" value="org.apache.tomcat.net.sslsocketfactory" /> <Parameter name="keystore" value="<path_for_.keystore>" /> <Parameter name="keypass" value="<keystore_password>" /> </Connector> Here, [path_for_.keystore]: Change the value of this parameter to the full path of.keystore file. [keystore_password]: The updated password of the keystore file. Configure OA to work with SSL Open the %PABASE%\stumbras\webapp\WEB-INF\web.xml file of OA and add the following XML fragment before web-app ends, that is </web-app> <security-constraint> <web-resource-collection> <web-resource-name>securedapp</web-resource-name> <url-pattern>/*</url-pattern> </web-resource-collection> <user-data-constraint> <transport-guarantee>confidential</transport-guarantee> </user-data-constraint> </security-constraint> Restart tomcat to finish the configuration. To restart tomcat perform the following: 1. Open windows services. 2. Stop and Start the Tomcat service. For OA and earlier: Stop and Start the Stumbras-Tomcat service. For OA and later: Stop and Start the Avaya OA Reporting Application service. Access OA by going to: ip address:8443/reports1/index.jsp 198 Installation and Configuration February 2017

199 Configuring SSL for OA ip address:8443/reports2/reptwriterui/ For more information, see Configuring SSL for Windows for OA and later Perform the following steps for configuring SSL for Windows: Generate the KeyStore file on page 199 Configure Tomcat for using the Keystore file on page 199 Configure OA to work with SSL on page 200 Generate the KeyStore file 1. Open command prompt type: cd %JAVA_HOME%/bin Run the keytool command: keytool -genkey -alias tomcat -keyalg RSA This command creates a new file in the home folder of the user under which you run it, named.keystore. To specify a different location or a file name, add the -keystore parameter, followed by the complete path to your keystore files as the following shows: keytool -genkey -alias tomcat -keyalg RSA \ -keystore \path\to\my\keystore 2. After running this command, you are prompted for the keystore password. The default password used by Tomcat is changeit. You can specify a custom password in the server.xml configuration file. 3. Answer all questions in the questionnaire. 4. Put the.keystore file in the webapp folder of OA. By default the.keystore file is in C:\Documents and Settings\ <username>\. Configure Tomcat for using the Keystore file 1. Open the server.oa.xml file located at %PABASE%\stumbras\tomcat\conf directory. 2. Find the Connector element tag that has attribute port=8999 and comment it. <!--Connector port="8999" protocol="http/1.1" /--> Installation and Configuration February

200 Chapter 4: Configuring Avaya OA subsystems and event collectors 3. Add a new Connector element that replaces the above HTTP based connector element as follows: <Connector protocol="org.apache.coyote.http11.http11nioprotocol" port="8443" maxthreads="150" SSLEnabled="true" scheme="https" secure="true" clientauth="false" sslprotocol="tls" keystorefile="[path_for_.keystore]" keystorepass="[password_for_keystore]"/> Here, [path_for_.keystore]: Change the value of this parameter to the full path of.keystore file. [keystore_password]: The updated password of the keystore file. Configure OA to work with SSL Open the %PABASE%\stumbras\webapp\WEB-INF\web.xml file of OA and add the following XML fragment before web-app ends, that is </web-app> <security-constraint> <web-resource-collection> <web-resource-name>securedapp</web-resource-name> <url-pattern>/*</url-pattern> </web-resource-collection> <user-data-constraint> <transport-guarantee>confidential</transport-guarantee> </user-data-constraint> </security-constraint> Restarting the Tomcat to finish the configuration 1. Click Start > Run. 2. In the Run window, type services.msc and press Enter. 3. In the Windows Services window search for OAReporting service. 4. Right-click OAReporting and select Restart. 200 Installation and Configuration February 2017

201 Configuring SSL for OA Access OA by going to: ip address:8443/reports1/index.jsp ip address:8443/reports2/reptwriterui/ For more information, see Configuring SSL for Solaris or AIX on OA and earlier Perform the following steps for configuring SSL for Solaris or AIX: AIX is supported only till OA Generate the KeyStore file on page 197 Configure Tomcat for using the Keystore file on page 197 Configure OA to work with SSL on page 198 Generate the KeyStore file 1. Open the shell in Solaris or AIX and type: cd $JAVA_HOME/bin Run the keytool command: keytool -genkey -alias avaya -keyalg RSA -keypass ttadmin -keystore keystore.bin -storepass ttadmin Change the highlighted words according to your requirements. However, ensure that both the keypass and storepass passwords are same. 2. Answer all questions in the questionnaire. A.bin file is created with the name provided keystore.bin, inside the bin folder located at: %JAVA_HOME%/bin 3. Put the.bin file in the webapps folder of Tomcat. Configure Tomcat for using the Keystore file 1. Open server.xml file located at opt/bi/stumbras/tomcat/conf/server.xml. 2. Find the Connector element / tag which has port 8443 and uncomment it if already not done. 3. Add the following highlighted attributes: Installation and Configuration February

202 Chapter 4: Configuring Avaya OA subsystems and event collectors <Connector port="8443" protocol="http/1.1" SSLEnabled="true" maxthreads="150" scheme="https" secure="true" clientauth="false" sslprotocol="tls" keystorefile="webapps/keystore.bin" keystorepass="ttadmin" /> Configure OA to work with SSL Open the web.xml file of OA and add the following XML fragment before web-app ends, that is </web-app> <security-constraint> <web-resource-collection> <web-resource-name>securedapp</web-resource-name> <url-pattern>/*</url-pattern> </web-resource-collection> <user-data-constraint> <transport-guarantee>confidential</transport-guarantee> </user-data-constraint> </security-constraint> Restart tomcat to finish the configuration. To restart tomcat perform the following: 1. Go to the bin folder of tomcat /opt/bi/stumbras/tomcat//bin and run the following commands: shutdown.sh start.sh Access OA by going to: ip address:8443/reports1/index.jsp ip address:8443/reports2/reptwriterui/ You can use OpenSSL for configuring SSL. For more information, see tomcat-6.0-doc/ssl-howto.html Configuring SSL for Solaris on OA and later Perform the following steps for configuring SSL for Solaris: 202 Installation and Configuration February 2017

203 Configuring SSL for Solaris on OA and later Generate the KeyStore file on page 201 Configure Tomcat for using the Keystore file on page 201 Configure OA to work with SSL on page 202 Generate the KeyStore file 1. Run the OA.profile /opt/bi/.profile as a root user. 2. Run the keytool command: keytool -genkey -alias avaya -keyalg RSA -keypass ttadmin -keystore keystore.bin -storepass ttadmin 3. Answer all questions in the questionnaire. A.bin file is created with the name provided keystore.bin, inside the bin folder located at: $OA_JRE_HOME/bin 4. Put the keystore.bin file in the $PABASE/stumbras/tomcat/webapps folder of tomcat directory. Configuring Tomcat for using the KeyStore file 1. Open the server.oa.xml file located at $PABASE/stumbras/tomcat/conf directory. 2. Find the Connector element tag that has attribute port=9080 and comment it. <!--Connector port="9080" protocol="http/1.1" /--> Installation and Configuration February

204 Chapter 4: Configuring Avaya OA subsystems and event collectors 3. Add a new Connector element that replaces the above HTTP based connector element as follows: <Connector protocol="org.apache.coyote.http11.http11nioprotocol" port="8443" maxthreads="150" SSLEnabled="true" scheme="https" secure="true" clientauth="false" sslprotocol="tls" keystorefile="webapps/keystore.bin" keystorepass="ttadmin" /> Configure OA to work with SSL Open the $PABASE/stumbras/webapp/WEB-INF/web.xml file of OA and add the following XML fragment before web-app ends: </web-app> <security-constraint> <web-resource-collection> <web-resource-name>securedapp</web-resource-name> <url-pattern>/*</url-pattern> </web-resource-collection> <user-data-constraint> <transport-guarantee>confidential</transport-guarantee> </user-data-constraint> </security-constraint> 204 Installation and Configuration February 2017

205 Changing the port number of the Tomcat server Restart tomcat to finish the configuration. 1. Go to the bin folder of tomcat $PABASE/stumbras/tomcat/bin and run the following commands: stopoareport.sh startoareport.sh 2. Access OA by going to: ip address:8443/reports1/index.jsp ip address:8443/reports2/reptwriterui/ For more information see Changing the port number of the Tomcat server On Windows Server, you must install Apache Tomcat for Basic Reports and use Tomcat as the default HTTP server. Apache Tomcat is bundled with Avaya OA 7.3.x. After you complete installing Avaya OA 7.3.x and making the reporting system functional, you must specify the port number 8999 in the reports URL to access the reports. For example, However, you can change the default HTTP port number. To change the default Apache HTTP port number: 1. On the reporting system, click Start > Run. 2. Type services.msc and click OK. 3. Search and Stop the Tomcat Service. In OA and earlier the Tomcat service name is Stumbras OA Reporting. In OA and later the Tomcat service name is Avaya OA Reporting Application. 4. Close the Services window. 5. In the Windows explorer, go the %PABASE%/stumbras/tomcat/conf folder. 6. Open the XML server.xml file for editing. For OA and earlier the XML file name is server.xml For OA and later the XML file name is server.oa.xml 7. In the XML file, search the 8999 string is a parameter value of the <Connector /> XML element. Installation and Configuration February

206 Chapter 4: Configuring Avaya OA subsystems and event collectors 8. Identify the XML element in which Normal HTTP connector is specified in the comments section. 9. Change the port number to the required value. Ensure that the port value that you specify is beyond the port value of standard TCP servers. 10. Restart the Tomcat service from the Windows Services interface. In OA and earlier the Tomcat service name is Stumbras OA Reporting. In OA and later the Tomcat service name is Avaya OA Reporting Application. 11. Specify the changed HTTP port number in the reports URL to access the Avaya OA reports. 206 Installation and Configuration February 2017

207 Chapter 5: Making changes to installed Avaya OA components You can change your OA installation by doing any of the following: Add: adds subsystems or adds client software that were not installed, or that were installed and then removed. Repair: repair corrupted files by reinstalling subsystems or the client software that were previously installed, thereby replacing the corrupted files. Move: move subsystems between servers. Remove: remove subsystems or the client software that were previously installed, or remove the entire OA software package. This section includes the following topics: Preparation checklist on page 208 Stopping or starting processes and services before making changes on page 209 Adding Avaya OA components on page 215 Repairing Avaya OA components on page 260 Moving subsystems on page 293 Changing subsystem attributes on page 301 Removing Avaya OA components on page 312 Important:! Important: If you are planning to upgrade your Avaya OA software to the latest version, do not do any additions or repairs to existing components until you first upgrade your Avaya OA software. For more information, see Avaya Interaction Center and Operational Analyst Release 7.3.x Upgrade and Migration Guide. Installation and Configuration February

208 Chapter 5: Making changes to installed Avaya OA components Preparation checklist Before you make any changes to your OA installation, follow these important steps and the recommendations. Procedure Have the original installation media available during the process. Before performing any OA change, Avaya recommends that you perform a backup of the database and the file systems. For a configuration that includes Avaya IC, verify the installation and configuration of the Avaya IC components and are running before you add, repair, configure, and run the OA components. For more information about Avaya IC planning and installation, see: Avaya Interaction Center Release 7.3.x Installation Planning and Prerequisites Avaya Interaction Center Release 7.3.x Installation and Configuration Verify that a minimum of 512 MB of free temporary space is available on the following: c: drive for Windows /var/tmp for Solaris /tmp folder for Linux /tmp for AIX. If this space is unavailable, the installer might not run successfully. Verify that at least 2 GB of free space is available on the server where you adding the Real-time subsystem. If installing the OA Source-Event Collector (EC) and Source-Event Collector Bridge (EC Bridge) subsystems on an Avaya IC server, verify that at least 100 MB of free disk space is available for the installation files. Before you make changes to the OA installation, turn off all virus scan software. SECURITY ALERT:! SECURITY ALERT: Temporarily turning off your virus scan software opens a potential risk for a virus attack. However, this risk can be low as the server is probably not being used simultaneously when you are installing the OA. After you complete the changes, remember to turn on the virus scan software. 208 Installation and Configuration February 2017

209 Stopping or starting processes and services before making changes Verify that no OA files are open. Procedure Verify that all OA Administration client users have logged off and closed the browser windows before you make changes to the OA software. Decide on the following while you are making changes to the installed components: Avaya recommends that you write down all user IDs and database names used when adding components. You need the information during configuration and when you make future changes. After installation, you can find most of this information using the oalist command. After adding the Administration client, you can customize the Administration client installation. For more information, see Customizing the Administration client on page 169. The system displays dialog boxes when making changes depending on what components you are installing. Stopping or starting processes and services before making changes Before you add, repair, move, or remove any OA components, you must stop certain processes on the server. You must stop the processes when you have the following on your server: Historical subsystem. Real-time subsystem. Report subsystem (basic). Source-CMS data collection software. Source-EC data collection software, or Source-EC Bridge. This section contains the following information: Determining which components are installed on your server on page 209 Stopping processes and services on page 210 Starting processes and services on page 212 Determining which components are installed on your server Before you stop processes or stop traffic for data collection, use the oalist command to display the components on your server. Installation and Configuration February

210 Chapter 5: Making changes to installed Avaya OA components To use the oalist command perform the following: 1. Enter the following commands:. /opt/bi/.profile (Solaris, RHEL, and AIX) oalist Stopping processes and services This section contains the following: Stopping processes and services on a Windows server on page 210 Stopping processes on a Solaris SPARC server on page 211 Stopping processes on RHEL server on page 211 Stopping processes on an AIX server on page 212 Stopping processes and services on a Windows server Based on which subsystems you install, use the following table to determine which procedures you use to stop processes and the services: Subsystems Historical Real-time Report Procedure 1. Log in as an administrative user. 2. In a command prompt window, enter pa stop all. 3. Select Start > Programs > Administrative Tools > Services. 4. Stop the Avaya Business Intelligence and ORBacus Naming services. 1. Log in as an administrative user. 2. In a command prompt window, enter pa stop all. 3. Select Start > Programs > Administrative Tools > Services. 4. Stop the following services: Avaya Business Intelligence ORBacus Naming Stumbras-Tomcat services (For OA and earlier) Avaya OA Reporting Application (For OA and later) 210 Installation and Configuration February 2017

211 Stopping or starting processes and services before making changes Subsystems Source-EC Source-EC Bridge Data API Utility Procedure 1. Log in as an administrative user. 2. From IC Manager, stop the Source-EC subsystems. 3. Select Start > Programs > Administrative Tools > Services. 4. Stop the ORBacus Naming service. 1. Log in as an administrative user. 2. In a command prompt window, enter pa stop all. Stopping processes on a Solaris SPARC server Based on which subsystems you install, use the following table to determine which procedures you use to stop processes and the services: Subsystems Historical Real-time Source-CMS Data API Utility Report Source-EC Procedure 1. Log in using an OA user ID and password. 2. Enter the following commands:. /opt/bi/.profile pa stop all 1. Log in using an OA user ID and password. 2. Enter the following commands:. /opt/bi/.profile pa stop all From IC Manager, stop the Source-EC subsystems. Stopping processes on RHEL server Based on which subsystems you install, use the following table to determine which procedures you use to stop processes and the services: Subsystems Source-CMS Data API Utility Procedure 1. Log in using an OA user ID and password. 2. Enter the following commands:. /opt/bi/.profile pa stop all Installation and Configuration February

212 Chapter 5: Making changes to installed Avaya OA components Stopping processes on an AIX server Based on which subsystems you install, use the following table to determine which procedures you use to stop processes and the services: Subsystems Historical Report Real-time Data API Utility Report Source-EC Procedure 1. Log in using an OA user ID and password. 2. Enter the following commands:. /opt/bi/.profile pa stop all 1. Log in using an OA user ID and password. 2. Enter the following commands:. /opt/bi/.profile pa stop all From IC Manager, stop the Source-EC subsystems. Starting processes and services This section contains the following: Starting processes and services on a Windows server on page 213 Starting processes on a Solaris SPARC server on page 214 Starting processes on RHEL server on page 214 Starting processes on an AIX server on page Installation and Configuration February 2017

213 Stopping or starting processes and services before making changes Starting processes and services on a Windows server Based on which subsystems you install, use the following table to determine which procedures you use to stop processes and the services: Subsystems Historical Real-time Report Source-EC Source-EC Bridge Data API Utility Procedure 1. Log in as an administrative user. 2. In a command prompt window, enter pa stop all. 3. Select Start > Programs > Administrative Tools > Services. 4. Start the Avaya Business Intelligence and ORBacus Naming services. 1. Log in as an administrative user. 2. In a command prompt window, enter pa stop all. 3. Select Start > Programs > Administrative Tools > Services. 4. Start the following services: Avaya Business Intelligence ORBacus Naming Stumbras-Tomcat services (For OA and earlier) Avaya OA Reporting Application (For OA and later) 1. Log in as an administrative user. 2. From IC Manager, stop the Source-EC subsystems. 3. Select Start > Programs > Administrative Tools > Services. 4. Start the ORBacus Naming service. 1. Log in as an administrative user. 2. In a command prompt window, enter pa start all. Installation and Configuration February

214 Chapter 5: Making changes to installed Avaya OA components Starting processes on a Solaris SPARC server Based on which subsystems you install, use the following table to determine which procedures you use to stop processes and the services: Subsystems Historical Real-time Source-CMS Data API Utility Report Source-EC Procedure 1. Log in using an OA user ID and password. 2. Enter the following commands:. /opt/bi/.profile pa start all 1. Log in using an OA user ID and password. 2. Enter the following commands:. /opt/bi/.profile pa start all From IC Manager, stop the Source-EC subsystems. Starting processes on RHEL server Based on which subsystems you install, use the following table to determine which procedures you use to stop processes and the services: Subsystems Source-CMS Data API Utility Procedure 1. Log in using an OA user ID and password. 2. Enter the following commands:. /opt/bi/.profile pa start all 214 Installation and Configuration February 2017

215 Adding Avaya OA components Starting processes on an AIX server Based on which subsystems you install, use the following table to determine which procedures you use to stop processes and the services: Subsystems Historical Report Real-time Data API Utility Report Source-EC Procedure 1. Log in using an OA user ID and password. 2. Enter the following commands:. /opt/bi/.profile pa start all 1. Log in using an OA user ID and password. 2. Enter the following commands:. /opt/bi/.profile pa start all From IC Manager, stop the Source-EC subsystems. Adding Avaya OA components You can add subsystems and the client software to an existing OA installation. When adding a subsystem or the client software, many of the installation option fields have data already populated from the original installation. Usually you cannot change that data. The procedure specified in this section does not include adding a Source-CMS data collection subsystem. For more information, see Installing Avaya OA components on a CMS server - Solaris SPARC on page 117. This section includes the following topics: License key considerations on page 216 Interactions on page 216 Adding Avaya OA components on page 216 Adding Avaya OA components on the CMS server with RHEL platform on page 238 Completing an addition to Avaya OA on page 243 Installation and Configuration February

216 Chapter 5: Making changes to installed Avaya OA components License key considerations When adding Avaya IC as a data source to a configuration that use to only received CMS data, you must upgrade to an Avaya IC and Avaya CMS Analytical license. To do this, you must reinstall (repair) the Historical subsystem, making sure to select Avaya IC as a data source. For more information, see Repairing Avaya OA components on page 260. Interactions When adding components to an existing installation, some you cannot add some combinations. This section describes those combinations and how to handle the interaction. Adding Report subsystem to Advanced Reporting subsystem and DB2 database: You can only install the Advanced Reporting subsystem on a Windows server. If the Advanced Reporting subsystem is on a server that is using a DB2 database installed on a dedicated AIX database server, you cannot add the basic Report subsystem to the same server where the Advanced Reporting subsystem is because the basic Report subsystem must use a database that Windows supports, Microsoft SQL or Oracle. If you must use a Windows server for the basic Report subsystem, you must first remove the Advanced Reporting subsystem before you add the basic Report subsystem. Adding new data collection source: If you must add a new data collection source, do a repair on the existing installation. For more information, see Repairing Avaya OA components on page 261. Adding Avaya OA components The procedures for adding Avaya OA software is almost identical for all operating systems. For this procedure, the Windows dialog boxes are shown and any differences for the other operating systems are described. To add OA components: 1. Stop all OA processes. For more information, see Stopping or starting processes and services before making changes on page Do one of the following to access and start the installation executable: 216 Installation and Configuration February 2017

217 Adding Avaya OA components CAUTION:! CAUTION: Install from a DVD drive that is local to the server where you are installing OA. Installing from a networked DVD drive is not supported. Operating System Windows Procedure 1. Log in with a user ID that has administration privileges. 2. If you install the Windows Terminal Services in Application mode, open a command prompt window and enter: change user /install CAUTION:! CAUTION: If you install the Windows Terminal Services in Administration mode, you cannot properly install any OA subsystem on that system. For more information, see Avaya Operational Analyst Release 7.3.x Installation Planning and Prerequisites. 3. Put the OA DVD in the drive. 4. Using Windows Explorer, navigate to the DVD drive and double-click the WinSetup.exe file. Installation and Configuration February

218 Chapter 5: Making changes to installed Avaya OA components Operating System Solaris Procedure 1. Log in as root. 2. Put the OA DVD in the drive and wait about 15 seconds. A file manager window displays the contents of the DVD. If the File Manager window does not open, enter the following commands to start the volume manager: /etc/init.d/volmgt stop /etc/init.d/volmgt start 3. From a terminal window, enter the following commands:. /opt/bi/.profile cd /cdrom/cdrom0./solsetup 218 Installation and Configuration February 2017

219 Adding Avaya OA components Operating System AIX Procedure 1. Log in as root. 2. To set the monitor display, enter: export DISPLAY=hostname:0.0 where hostname is the name of the server. 3. If you are adding the Historical subsystem, enter the following commands to set the DB2 environment: - As the instance owner, or any member of DB2 SYSADM group: export EXTSHM=ON db2set DB2ENVLIST=EXTSHM db2stop db2start - As the user launching the OA Installation (root): # export EXTSHM=ON #./AixSetup 4. Put the OA DVD in the drive and wait about 15 seconds. export LANG=en_US. /opt/bi/.profile mkdir /cdrom (if this folder does not already exist) mount -v cdrfs -r /dev/cd0 /cdrom cd /cdrom./aixsetup After several seconds, the Initializing wizard window displays, followed by the Welcome dialog box. Important:! Important: You can stop the installation anytime by clicking Cancel before you run the actual installation of files (see Step 48). If you click Cancel, you are asked to confirm your intention to cancel. If you cancel, the installation is terminated and the system is restored to its previous state. 3. Click Next. The License Key dialog box displays. 4. Enter the provided license key for the components purchased. Installation and Configuration February

220 Chapter 5: Making changes to installed Avaya OA components 5. Click Next. The License Agreement dialog box displays. 6. Select I accept the terms in the license agreement. 7. Click Next. The User Information dialog box displays. The Domain field only displays for Windows systems. 8. Enter and confirm the password for the installed user ID. 9. Click Next. You might get this screen if you are adding the EC subsystem for the first time. Provide the location where you install IC. This location enables the OA installer to recognize that IC is on the system. 220 Installation and Configuration February 2017

221 Adding Avaya OA components If you leave the field blank, OA installer cannot install EC and ECB subsystems on the system. 10. Click Next. There might be a long delay before the next dialog box displays. The Feature Selection dialog box displays. This dialog box indicates the components that were previously installed. In this example, the Historical subsystem, Report subsystem, and Administration client are already installed. 11. Select which components to add. Installation and Configuration February

222 Chapter 5: Making changes to installed Avaya OA components Important:! Important: After selecting or clearing a check box, there might be a delay before the dialog box refreshes and you see the check mark or the check mark is cleared. This delay might take a few seconds. Do not select or clear another check box until the dialog box refreshes and you can see whether the check box is select or clear. Do not select installed any components. To repair an already installed component, see the procedure Repairing Avaya OA components on page 260. The following example shows the Feature Selection dialog box with the Real-time subsystem, Data API Utility, and Advanced Reporting subsystem selected: 222 Installation and Configuration February 2017

223 Adding Avaya OA components 12. Click Next. The ADS Configuration dialog box displays: 13. Administer the dialog box as shown in the following table: Field ADS Version ADS Port OA Administration Group Distinguished Name (DN) Description Enter the LDAP version the authentication server is using. OA supports versions 2 and 3, with the default set to 3. Enter the port number used for ADS. OA defaults to 389, which is the default when you install ADS. Enter the DN for the administration group. For typical example of ADS setup, if you use the default group named oaadmin, a domain named oalab, and the company name is Telco, you enter: CN=oaadmin,CN=Users,DC=oalab,DC=telco,DC=com If you are not using ADS, use the following format for the DN: localhost\oaadmin Installation and Configuration February

224 Chapter 5: Making changes to installed Avaya OA components Field OA Report Group Distinguished Name (DN) OA Report Writer Group Distinguished Name (DN) Description Enter the DN for the report group. For typical example of ADS setup, if you use the default group named oarpt, a domain named oalab, and the company name is Telco, you enter: CN=oarpt,CN=Users,DC=oalab,DC=telco,DC=com If you are not using ADS, use the following format for the DN: localhost\oarpt Enter the DN for the report writer group. For typical example of ADS setup, if you use the default group named oawriter, a domain named oalab, and the company name is Telco, you enter: CN=oawriter,CN=Users,DC=oalab,DC=telco,DC=com If you are not using ADS, use the following format for the DN: localhost\oawriter 14. Click Next. If you are adding the Historical subsystem or the Report subsystem, the Reports Configuration dialog box displays. If you are not adding the Historical subsystem or the Report subsystem, continue with Step For Solaris and AIX, enter the installation data for the Web server software. See the following table for AIX field information: Field DB2 Version Description Select from the drop-down box which version of DB2 you are using for the historical database. The DB2 Version field displays only if you install the Report subsystem on a server without the Historical subsystem. 16. Click Next. 17. A warning message might display about deleting the TimesTen database log files. Follow any instructions shown. When you finish, click OK. 224 Installation and Configuration February 2017

225 Adding Avaya OA components 18. The Historical Server Configuration dialog box displays. The fields that appear on the Historical Server Configuration dialog box vary depending on your selections. 19. Administer the dialog box as shown in the following table: Field Historical Subsystem Server Name Historical Database Server Name Do one of the following: Description If you are installing the Historical subsystem, the system displays the name of this server and you cannot change the name. If you are not installing the Historical subsystem, enter the fully qualified domain name of the system where you install the Historical subsystem. Do one of the following: If the Historical database is on the same system where you install the Historical subsystem is, enter the system name. If the Historical database is on a different system than where you install the Historical subsystem is, enter the fully qualified domain name for the system where you install the Historical database is. You must manually create the filegroups or tablespaces on the Historical database server before this installation might continue. For more information, see Avaya Operational Analyst Release 7.3.x Installation Planning and Prerequisites. Installation and Configuration February

226 Chapter 5: Making changes to installed Avaya OA components Field Please choose a Historical Database Create Historical Tables for these Collection Sources Alarm Services Select the appropriate database. If the system can identify the database type based on the Historical Database Server Name, the database type is the only type listed. Select the collection sources for the historical tables. You can collect data from Avaya IC, CMS, or both depending on what your product license allows. If you are using a backend database, you must create filegroups or tablespaces for Avaya IC, CMS obefoterior to selecting collection sources. For more information, see Avaya Operational Analyst Release 7.3.x Installation Planning and Prerequisites. Description You cannot remove these collection sources when adding components to an OA installation. To send alarm data to the Avaya IC server, click the IC box under Alarm Services. Then enter the fully qualified domain name of the server where you install the Source-ECsubsystem is in the Server Name field. For an OA and CMS configuration without Avaya IC, leave these options blank. 20. Click Next. 21. If you are adding the Historical or Report subsystem, the Database Configuration dialog box displays. The installer displays the following screen in OA Release 7.3, 7.3.1, and Installation and Configuration February 2017

227 Adding Avaya OA components The installer displays the following screen in OA Release Important:! Important: If you are adding the Historical subsystem to a server that is separate from the Historical database, you must first install the database client software. The database client software is mandatory for Historical subsystem for coresident/ distributed setups. 22. Use the following information to complete the dialog box. Use the values from your database installation, which is described in Avaya Operational Analyst Release 7.3.x Installation Planning and Prerequisites. Some of the fields may include default values. Field Oracle Microsoft SQL DB2 DB Administrator Password Password for the sys user ID. Password for the sa user ID. N/A OA DB User ID User ID for the OA database. OA creates this user ID during a new installation. User ID for the OA database. OA creates this User ID during a new installation. User ID for the OA database. OA creates this user ID during a new installation. OA DB User Password User password for the OA database. User password for the OA database. User password for the OA database. Installation and Configuration February

228 Chapter 5: Making changes to installed Avaya OA components Field Oracle Microsoft SQL DB2 OA Database Name New database name that the system creates during install, for example, oadb. New database name that the system creates during install, for example, oadb. The database name specified when you install DB2 and create an instance. IC DB User ID 1 Existing Avaya IC user ID for the Avaya IC Repository database. For example, repository. Existing Avaya IC user ID for the Avaya IC Repository database. For example, repository. Existing Avaya IC user ID for the Avaya IC Repository database. For example, db2inst1. IC DB User Password 1 User password for the Avaya IC Repository user ID User password for the Avaya IC Repository user ID User password for the Avaya IC Repository user ID IC Repository Database 1 Avaya IC Repository database name. For example, repository. Avaya IC Repository database name. For example, repository. Avaya IC Repository database/schema name. For example, repository. DB Instance Name Avaya IC and OA database instance name. Avaya IC and OA database instance name. MSSQLSERVER if you used the default database instance. Avaya IC and OA database instance name. For example, db2instl, which is the default. TCP/IP Port Number If using the default configuration, otherwise the port number specified during database installation If using the default configuration, otherwise the port number specified during database installation. Port number assigned to the database instance creation during the DB2 installation. If you are unsure of the number, check /etc/services and look for the DB2 instance name. The port number is included. Oracle TNS Server Name A valid TNS server name. The database administrator assigns this name during Oracle installation. The default name is dbservername.oadb. You must check the tnsnames.ora file and use the exact entry found there. If an entry is not found, ask the DBA to create a tnsnames.ora entry and then use the exact entry found there. N/A N/A 228 Installation and Configuration February 2017

229 Adding Avaya OA components Field Oracle Microsoft SQL DB2 SQL Server DataBase Name N/A New Microsoft SQL database created during installation N/A Installation and Configuration February

230 Chapter 5: Making changes to installed Avaya OA components Field Oracle Microsoft SQL DB2 Oracle_Home (Client) This filed refers to the Oracle DB client home location. This field is applicable on OA Release N/A N/A Ensure that the tnsnames.ora file exists on the server where OA Historical is being installed. This file is found in the following location: ORACLE_HOME / network/admin of the Oracle Client installation. If this file does not exist, then you will need to create it. On Solaris platform, when Oracle client is installed, the tnsnames.ora file does not exist. Ensure that the tnsnames.ora file is created with correct set of permissions (666) and with suitable owner/ group ownership, [oracle/oinstall] Ensure that the Oracle Client Home selected is of the compatible version that OA would use to connect to the appropriate DB Server. Refer to the Oracle documentation to check on the compatibility matrix for client/server connectivity. On Windows server where OA historical subsystem is installed, ensure that Windows environmental path variable (PATH) has the path of the Oracle Home (Client). 230 Installation and Configuration February 2017

231 Adding Avaya OA components 1. This field does not display if you do not use Avaya IC as a collection source. During the creation of the Repository Database using Oracle as your database software, the system asks you to provide a password for the Repository database. Use this name as your IC DB User ID with the password you enter. 23. Click Next. One of the following occurs: For Oracle, continue with Step 24. For Microsoft SQL, continue with Step 27. For AIX, continue with Step A warning dialog box about the Oracle archive log might display. 25. Click OK to acknowledge the warning, if displayed. 26. For Oracle, the system looks through the TNSnames.ora file to determine if the TNS server name is within that file. If server name is within the file, then install continues with Step 31. If the server name is not in the file, the following warning message displays asking if you want the installation program to change the TNSnames.ora file to include the TNS server name. If you select No, you return to the Database Configuration dialog box. You can go no further until you resolve the TNS server name issue. If you select Yes, the installation program attempts to edit the file. One of the following occurs: - If the TNSnames.ora file has write permission then the system changes the file to include the administered TNS server name and the install continues. - If the permissions on the TNSnames.ora file are read-only, the system cannot change the file. The system then displays the message stating that you must change the permission on the file manually. Select OK to return to the Database Configuration dialog box. You must change permissions on the file to continue with the install. There might be a long delay before the next dialog box displays. Installation and Configuration February

232 Chapter 5: Making changes to installed Avaya OA components 27. The following dialog box displays when using Microsoft SQL Server. If you are not using Microsoft SQL, continue with Step Select Use Existing DB to use an existing database. 29. If you choose to not use the existing database, enter the size and location of the Microsoft SQL Server Transaction Log. You can use the default locations. 30. Click Next. If you are adding the Historical subsystem, the next step is to configure tablespaces. Important:! Important: If the database is on a back-end database server, none of the dialog boxes shown in this section displays. Continue with Step Installation and Configuration February 2017

233 Adding Avaya OA components 31. The OA Common Table Spaces dialog box displays. 32. Enter the correct location and the size for each filegroup or tablespace. For more information, see Avaya Operational Analyst Release 7.3.x Installation Planning and Prerequisites. If the filegroups and tablespaces do not already exist, the Use Existing checkboxes does not display. Also the Location and Size input fields include default values you can edit. If the filegroups and tablespaces do already exist, the Use Existing checkboxes are selected. You can clear the checkboxes and enter a different location and different size. Installation and Configuration February

234 Chapter 5: Making changes to installed Avaya OA components 33. Click Next. If data is collected from CMS, the OA CMS Specific dialog box displays. 34. Enter the correct location and the size for each filegroup or tablespace. For more information, see Avaya Operational Analyst Release 7.3.x Installation Planning and Prerequisites. If the filegroups and tablespaces do not already exist, the Use Existing checkboxes does not display. Also the Location and Size input fields include default values you can edit. If the filegroups and tablespaces do already exist, the Use Existing checkboxes are selected. You can clear the checkboxes and enter a different location and different size. 234 Installation and Configuration February 2017

235 Adding Avaya OA components 35. Click Next. If data is collected from Avaya IC, the OA IC Specific dialog box displays. 36. Enter the correct location and the size for each filegroup or tablespace. For more information, see Avaya Operational Analyst Release 7.3.x Installation Planning and Prerequisites. If the filegroups and tablespaces do not already exist, the Use Existing checkboxes does not display. Also the Location and Size input fields include default values you can edit. If the filegroups and tablespaces do already exist, the Use Existing checkboxes are selected. You can clear the checkboxes and enter a different location and different size. 37. Click Next. A warning message concerning the storage of Historical data on one disk might display. 38. Click OK to acknowledge the warning, if displayed. 39. One of the following occurs: If you are not adding a Real-time subsystem, continue with Step 43. Installation and Configuration February

236 Chapter 5: Making changes to installed Avaya OA components If you are adding a Real-time subsystem, the Real-time Configuration dialog box displays. Important: 40. In the Real Time DB Location field, Avaya recommends that you enter a path that is on a different disk drive from where you install the OA software is. The disk drive must have at least 2.2 GB of free disk space. 41. In the Real Time DB Size(M) field, the only option is Click Next.! Important: If you do not have at least 2.2 GB of free disk space to install TimesTen, a warning message displays. You cannot continue until at least 2.2 GB of disk space is available. 43. If you are adding the Administration client, Windows only, the Administration client locale settings dialog box displays. If you are not adding the Administration client, continue with Step Select a locale setting from the drop-down list. 45. Click Next. 46. The system displays Installation Preview dialog box listing the components you have selected. 47. Scroll through the preview dialog box to verify the selected components and the configuration data. 236 Installation and Configuration February 2017

237 Adding Avaya OA components CAUTION: Important:! CAUTION: Do not close the Progress dialog box after you have clicked Next in the following step. If you close the Progress dialog box after the installation has started, you disrupt the installation. You must contact Avaya support to do a manual cleanup of the installation. 48. Click Next to start the installation. The Progress dialog box displays showing the progress of the installation, which takes several minutes. Near the end of the installation, the dialog box can go blank for some time. When the installation is complete, the Install Complete dialog box displays. 49. Click Next. On Solaris and AIX, the Install Complete dialog box closes and the addition is complete. On Windows, the Restart System dialog box displays. Before you restart the server, ensure you save a copy of the server.properties file if the file is deleted during the restart. Perform the following: 1. Open Windows Explorer. 2. Navigate to %PABASE%\BI\data\admin. 3. Copy the server.properties file onto the Windows clipboard. 4. Go to your Windows desktop or some other location other than the OA installation folder and then paste the server.properties file there.! Important: You must always restart a Windows server this time for OA to operate properly. If you are not requested to restart the server, you must manually restart the server. 5. Return to the Restart System dialog box, select the option to restart your system now, and click Next. 6. After the system restarts, navigate to %PABASE%\BI\data\admin. 7. Verify that the server.properties file is in the folder. 8. If the file is not in the folder, go to the location where you saved a copy of server.properties and copy the file onto the Windows clipboard. 9. Navigate to %PABASE%\BI\data\admin. 10. Paste the server.properties file into the folder. 50. Perform one of the following: On Windows, press the eject button on the DVD drive, remove the DVD, and store it in a safe location. Installation and Configuration February

238 Chapter 5: Making changes to installed Avaya OA components On Solaris, close all, but one terminal window and enter: cd / eject cdrom On AIX, close all, but one terminal window and enter: cd / umount /cdrom 51. Press the eject button on the DVD drive (AIX only). 52. Remove the OA DVD and store it in a safe location. 53. If you added the Report subsystem, remember to install the Report client support files. For more information, see Installing and testing the Report client on page 153. Adding Avaya OA components on the CMS server with RHEL platform The procedures for adding Avaya OA software is almost identical for all operating systems. For this procedure, the Windows dialog boxes display and any differences for the other operating systems are described. To add OA components perform the following: 1. Stop all OA processes. For more information, see Stopping or starting processes and services before making changes on page Change the folder to the location from where you want to install Avaya OA components. CAUTION: Important:! CAUTION: Install from a CD/DVD drive that is local to the server where you are installing OA. Installing from a networked DVD drive is not supported. After several seconds, the Initializing wizard window displays, followed by the Welcome dialog box.! Important: You can stop the installation any time by clicking Cancel before you run the actual installation of files. If you click Cancel, you are asked to confirm your intention to cancel. If you cancel, the system stops the installation and restores the system to the previous state. 3. From a terminal window, enter the following commands:./linsetup 238 Installation and Configuration February 2017

239 Adding Avaya OA components 4. Click Next. The License Key dialog box displays. 5. Enter the provided license key for the components purchased. 6. Click Next. The License Agreement dialog box displays. 7. Select I accept the terms in the license agreement. 8. Click Next. The User Information dialog box displays. 9. Enter User Password and Confirm the password for the installed user ID. Installation and Configuration February

240 Chapter 5: Making changes to installed Avaya OA components 10. Click Next. The Feature Selection dialog box displays. The dialog box indicates the components that were previously installed. In this example the Source - CMS Subsystem component is already installed. 11. Select the components you want to add. Important: Important:! Important: You can install each component or multiple components in a combination. However, if you are installing Data API Utility, you must select the Source - CMS Subsystem option.! Important: After selecting or clearing a check box, there might be a delay before the dialog box refreshes and you see the check mark or the check mark is cleared. This delay might take a few seconds. Do not select or clear another check box until the dialog box refreshes and you can see that the check box is select or clear. Do not select any components that are already installed. To repair an already installed component, see the procedure Repairing Avaya OA components on page Installation and Configuration February 2017

241 Adding Avaya OA components 12. Click Next. A warning message might display about deleting the TimesTen database log files. Follow any instructions shown. When complete, click OK. The Historical Server Configuration dialog box displays. 13. Administer the dialog box as shown in the following table: Field Historical Subsystem Server Name Alarm Services Description Enter the fully qualified domain name of the system where you install the Historical subsystem is. To send alarm data to the Avaya IC server, click the IC box under Alarm Services. Then enter the fully qualified domain name of the server where the Source-EC subsystem is installed in the Server Name field. For an OA and CMS configuration without Avaya IC, leave these options blank. 14. Click Next. There might be a long delay before the next dialog box displays. Installation and Configuration February

242 Chapter 5: Making changes to installed Avaya OA components 15. Click Next. The system displays the dialog box for specifying the CMS password. CAUTION: 16. Click Next. The system displays the Installation Preview dialog box listing the components you have selected. 17. Scroll through the preview dialog box to verify the selected components and the configuration data.! CAUTION: Do not close the Progress dialog box after you have clicked Next in the following step. If you close the Progress dialog box after the installation has started, the installation will be disrupted and you must contact Avaya support to do a manual cleanup of the installation. 18. Click Next to start the installation. The Progress dialog box displays showing the progress of the installation, which takes several minutes. Near the end of the installation, the dialog box goes blank for some time. When the installation is complete, the Install Complete dialog box displays. 19. Click Next. 20. If you are installing the software from the CD/DVD, close all, but one terminal window and enter: cd / eject cdrom 21. Remove the Avaya OA CD/DVD. 242 Installation and Configuration February 2017

243 Adding Avaya OA components Completing an addition to Avaya OA Depending on the platform you are using, use the procedures in the following sections to complete your addition: To complete an addition to a Windows system on page 243 To complete an addition to a Solaris system on page 246 To complete an addition to the RHEL system on page 252 To complete an addition to an AIX system on page 254 To complete an addition to a Windows system 1. Log in using an OA user ID and password. For more information, see Avaya Operational Analyst Release 7.3.x Installation Planning and Prerequisites. 2. Open a command prompt window. 3. If Terminal Services is enabled, enter: change user /execute 4. In the command prompt window, enter the following command to show what processes are running: pa list The system displays a message similar to the following:. system boot Dec 20 07:54. run-level 4 Dec 31 10:23 4 java. Dec 20 07: id=admb java. Dec 20 07: id=adm0 java. Jan 02 16: id=ams java. Dec 20 07: id=aut java. Dec 20 07: id=schd... There can be several Java entries, and these lines cannot have an exit code at the end of the line. If the system displays any exit codes on the Java entries, that process is not running. Escalate the problem to Avaya Technical Support. The id=aut and id=schd displays when you have installed the Historical subsystem. Installation and Configuration February

244 Chapter 5: Making changes to installed Avaya OA components The recorder entries display only if you are collecting data from CMS or Avaya IC. Forwarder entries might display on a server that you have installed the Real-time subsystem installed. 5. If you get the message mom is not active, enter: pa start all 6. Repeat Step 4 to verify that OA has started. 244 Installation and Configuration February 2017

245 Adding Avaya OA components 7. Enter: oalist The system displays a message similar to the following: Subsystems installed Historical Real Time Reports Data API Utility Source-EC Advanced Reports Administration Client Server Names Historical: punoasvorsr03 Historical Database: <IP_Address_of_Historical_Database_System> Database information Type: MSSQL AdminID: sa UserID: oadba Instance Name: MSSQLSERVER Port Number: 1433 OA DB Name: oadb IC UserID: repository IC Repository DB Name: repository Using a Backend/Remote Database IC Historical Tables created User information OA User ID: biadmin Domain: punoadom Group ID: oaadmin Active Directory Server or Localhost Information ADS Version: 3 ADS Port: 389 ADS Admin Group: CN=oaadmin,OU=OA Admins,DC=punoadom,DC=avaya,DC=com ADS Report Group: CN=oarpt,OU=OA Admins,DC=punoadom,DC=avaya,DC=com ADS Report Writer Group: CN=oawriter,OU=OA Admins,DC=punoadom,DC=avaya,DC=com Admin Client Locale Admin Client Locale: en_us OA Software information Version Installed: Select Start > Programs > Administrative Tools > Services. 9. Validate that the following services are running and are set to run automatically. If the services are not administered to run automatically, administer the services as such. If you have installed the Historical subsystem, check for the following: Installation and Configuration February

246 Chapter 5: Making changes to installed Avaya OA components - Avaya Business Intelligence Service - ORBacus Naming Service If you have installed the Real-time subsystem, check for the following: - Avaya Business Intelligence Service - ORBacus Naming Service - TimesTen Data Manager If you have installed the Report subsystem, check for the following: - Avaya Business Intelligence Service - ORBacus Naming Service - Stumbras-Tomcat (For OA and earlier) - Avaya OA Reporting Application (For OA and later) If you have installed the Source-EC subsystem, check for the following: - ORBacus Naming Service 10. If you are not successful starting OA, see Avaya Operational Analyst Release 7.3.x Maintenance and Troubleshooting Guide for more troubleshooting information. To complete an addition to a Solaris system CAUTION: 1. Log out of the desktop environment. 2. Log in using an OA user ID and password. For more information, see Avaya Operational Analyst Release 7.3.x Installation Planning and Prerequisites.! CAUTION: Do not use any OA commands while logged in as root. Using the root login ID on these commands changes ownership of files and makes the files unusable by the OA user ID. 3. Enter:. /opt/bi/.profile 246 Installation and Configuration February 2017

247 Adding Avaya OA components 4. Enter the following command to determine what processes are running: pa list The system displays a message similar to the following:. system boot Dec 20 07:54. run-level 4 Dec 31 10:23 4 java. Dec 20 07: id=admb java. Dec 20 07: id=adm0 java. Jan 02 16: id=ams java. Dec 20 07: id=aut java. Dec 20 07: id=schd... There can be several Java entries, and these lines cannot have an exit code at the end of the line. If the system displays any exit codes on the Java entries, that process is not running. Escalate the problem to Avaya Technical Support. The id=aut and id=schd only displays when you have installed the Historical subsystem. The recorder entries display only if you are collecting data from CMS or Avaya IC. Forwarder entries might display on a server that you have installed the Real-time subsystem. 5. If you get the message mom is not active, enter: pa start all 6. Repeat Step 4 to verify that OA has started. 7. If you are not successful starting OA, see Avaya Operational Analyst Release 7.3.x Maintenance and Troubleshooting Guide for more troubleshooting information. Installation and Configuration February

248 Chapter 5: Making changes to installed Avaya OA components 8. Enter: oalist The system displays a message similar to the following: Subsystems installed Historical Real Time Reports Data API Utility Source-EC Server Names Historical: puoadvsolsr14 Historical Database: <IP_Address_of_Historical_Database_System> Reports: puoadvsolsr14 Database information Type: ORACLE AdminID: sys UserID: oadba Instance Name: oa7211g Port Number: 1521 IC UserID: repository Using a Backend/Remote Database IC Historical Tables created User information OA User ID: biadmin Group ID: oaadmin Reports information Reports Group ID: oarpt Report Writer Group ID: oawriter Tomcat Home: /home/biadmin/bi/stumbras/tomcat Tomcat Port: 9080 OA Software information Version Installed: If you have installed the Historical subsystem, use the following commands and responses to verify that the required services are running. If the services are not running, escalate the problem using the normal channels. a. Enter the following command to determine if the Avaya Business Intelligence Service is running: ps -ef grep initsrv The system displays a message similar to the following: root Dec 27? 0:06 /opt/bi/bin/initsrv -n oaadmin -v 30 biadmin :28:00 pts/11 0:00 grep initsrv 248 Installation and Configuration February 2017

249 Adding Avaya OA components b. Enter the following command to determine if the ORBacus Naming Service is running: ps -ef grep naming The system displays a message similar to the following: biadmin Oct 21? 6:48 /export/home/biadmin/ jre<version_number>/bin/java -Dooc.naming.port=10000 com.ooc.cosn biadmin :27:35 pts/3 0:00 grep naming 10. If you have installed the Real-time subsystem, use the following commands and responses to verify that the required services are running. If the services are not running, escalate the problem using the normal channels. a. Enter the following command to determine if the Avaya Business Intelligence Service is running: ps -ef grep initsrv The system displays a message similar to the following: root Dec 27? 0:06 /opt/bi/bin/initsrv -n oaadmin -v 30 biadmin :28:00 pts/11 0:00 grep initsrv b. Enter the following command to determine if the ORBacus Naming Service is running: ps -ef grep naming The system displays a message similar to the following: biadmin Oct 21? 6:48 /export/home/biadmin/ jre<version_number>/bin/java -Dooc.naming.port=10000 com.ooc.cosn biadmin :27:35 pts/3 0:00 grep naming c. Enter the following command to determine if the TimesTen Data Manager is running: ps -ef grep timesten The system displays a message similar to the following: root Dec 23? 0:01 /export/home/biadmin/timesten5.1.34/ TimesTen/avaya_bi/bin/timestend root Dec 23? 0:00 /export/home/biadmin/timesten5.1.34/ TimesTen/avaya_bi/bin/timestensubd -id 0 root Dec 23? 0:00 /export/home/biadmin/timesten5.1.34/ TimesTen/avaya_bi/bin/timestensubd -id 1 root Dec 23? 0:00 /export/home/biadmin/timesten5.1.34/ TimesTen/avaya_bi/bin/timestensubd -id 2 root Dec 23? 0:00 /export/home/biadmin/timesten5.1.34/ TimesTen/avaya_bi/bin/timestensubd -id 3 biadmin :34:22 pts/11 0:00 grep timesten Installation and Configuration February

250 Chapter 5: Making changes to installed Avaya OA components 11. If you have installed the Source-EC subsystem, use the following commands and responses to verify that the required services are running. If the services are not running, escalate the problem using the normal channels. a. Enter the following command to determine if the ORBacus Naming Service is running: ps -ef grep naming The system displays a message similar to the following: biadmin Oct 21? 6:48 /export/home/biadmin/ jre<version_number>/bin/java -Dooc.naming.port=10000 com.ooc.cosn biadmin :27:35 pts/3 0:00 grep naming 12. If you have installed the Report subsystem, enter the following commands to stop and restart the Tomcat software:. /opt/bi/.profile cd /opt/bi/stumbras/tomcat/bin For OA and earlier:./shutdown.sh./startup.sh For OA and later:./stopoareport.sh./startoareport.sh 13. If you have installed the Report subsystem, use the following commands and responses to verify that the required services are running. If the services are not running, escalate the problem using the normal channels. a. Enter the following command to determine if the Avaya Business Intelligence Service is running: ps -ef grep initsrv The system displays a message similar to the following: root Jan 20? 0:06 /opt/bi/bin/initsrv -n oaadmin -v 30 biadmin :28:00 pts/11 0:00 grep initsrv b. Enter the following command to determine if the ORBacus Naming Service is running: ps -ef grep naming The system displays a message similar to the following: biadmin Oct 21? 6:48 /export/home/biadmin/ jre<version_number>/bin/java -Dooc.naming.port=10000 com.ooc.cosn biadmin :27:35 pts/3 0:00 grep naming 250 Installation and Configuration February 2017

251 Adding Avaya OA components 14. If you have installed the Source-EC subsystem, use the following commands and responses to verify that the required services are running. If the services are not running, escalate the problem using the normal channels. a. Enter the following command to determine if the ORBacus Naming Service is running: ps -ef grep naming The system displays a message similar to the following: biadmin Jan 20? 6:48 /export/home/biadmin/ jre<version_number>/bin/java -Dooc.naming.port=10000 com.ooc.cosn biadmin :27:35 pts/3 0:00 grep naming CAUTION: 15. Start the Tomcat server after you configure the Admin client. For more information, see Administration client options on page 168. a. Log in to the Solaris system using an Avaya OA user ID and password. For more information, see Avaya Operational Analyst Release 7.3.x Installation Planning and Prerequisites.! CAUTION: Do not use any Avaya OA commands while logged in as root. Using the root login ID on these commands changes ownership of files and makes them unusable by the Avaya OA user ID. b. Enter the command:./opt/bi/.profile. c. Go to the Tomcat server location. Enter the command: cd /opt/bi/stumbras/tomcat/bin. d. Start the Tomcat server. Enter the command: For OA and earlier:./startup.sh For OA and later:./startoareport.sh 16. Check the Tomcat server logs to verify that Tomcat is running successfully. a. Go to the $PABASE/stumbras/tomcat/logs/ folder. b. Enter the command: vi catalina.out 17. Check if the Tomcat server is running successfully. a. Go to the $PABASE/stumbras/tomcat/conf folder. Installation and Configuration February

252 Chapter 5: Making changes to installed Avaya OA components b. Check if the PID.txt file is present in the folder. The PID.txt file indicates that the process ID of the Tomcat server is registered in the PID.txt file. 18. Stop the Tomcat server. a. Enter the command:./opt/bi/.profile. b. Go to the Tomcat server location. Enter the command: cd /opt/bi/stumbras/tomcat/bin. c. Stop the Tomcat server. Enter the command: For OA and earlier:./shutdown.sh -force For OA and later:./stopoareport.sh -force To complete an addition to the RHEL system CAUTION: 1. Log out of the desktop environment. 2. Log in to the system using an Avaya OA user ID and password. For more information, see Avaya Operational Analyst Release 7.3.x Installation Planning and Prerequisites.! CAUTION: Do not use any Avaya OA commands while logged in as root. Using the root login ID on these commands changes ownership of files and makes them unusable by the Avaya OA user ID. 3. Enter:. /opt/bi/.profile 4. Enter the following command to determine if the Avaya Business Intelligence Service is running: ps -ef grep initsrv The system displays a message similar to the following: root :12? 00:00:00 /opt/bi/bin/initsrv -n oaadmin -v Installation and Configuration February 2017

253 Adding Avaya OA components 5. Enter the following command to determine if the ORBacus Naming Service is running: ps -ef grep CosNaming The system displays a message similar to the following: root :12? 00:00:00 /export/home/biadmin/ jre<version_number>/bin/java com.ooc.cosnaming.server -IIOPport Enter the following command to show what processes are running: pa list The system displays a message similar to the following: (cmsjune74)-(root)=# pa list all. system boot Oct 1 17:13. run-level 4 Oct 1 17:13 4 java. Oct 1 17:13 old id=admb java. Oct 1 17:13 old id=adm0 java. Oct 1 17:13 old id=ams There can be several Java entries, and these lines cannot have an exit code at the end of the line. If the system displays any exit codes on the Java entries, that process is not running. Escalate the problem to Avaya Technical Support. The id=aut and id=schd only displays when you have installed the Historical subsystem. The recorder entries display only if you are collecting data from CMS or Avaya IC. Forwarder entries might display on a server that you have installed the Real-time subsystem. 7. If you get the message mom is not active, enter: pa start all 8. Repeat Step 4 to verify Avaya OA is running. If you are not successful starting Avaya OA, see Avaya Operational Analyst Release 7.3.x Maintenance and Troubleshooting Guide for more troubleshooting information. Installation and Configuration February

254 Chapter 5: Making changes to installed Avaya OA components 9. Enter the following command: oalist The system displays a message similar to the following. Subsystems installed Data API Utility Source-CMS Server Names Historical: icdev84 Database information Type: UNSET User information CMS ID: informix OA User ID: biadmin Group ID: oaadmin OA Software information Version Installed: To complete an addition to an AIX system 1. Log out of the desktop environment. 2. Log in using an OA user ID and password. For more information, see Avaya Operational Analyst Release 7.3.x Installation Planning and Prerequisites. CAUTION:! CAUTION: Do not use any OA commands while logged in as root. Using the root login ID on these commands changes ownership of files and makes them unusable by the OA user ID. 3. Enter:. /opt/bi/.profile 4. Enter the following command to show what processes are running: pa list The system displays a message similar to the following:. system boot Dec 20 07:54. run-level 4 Dec 31 10:23 4 java. Dec 20 07: id=admb java. Dec 20 07: id=adm0 java. Jan 02 16: id=ams java. Dec 20 07: id=aut java. Dec 20 07: id=schd 254 Installation and Configuration February 2017

255 Adding Avaya OA components There can be several Java entries, and these lines cannot have an exit code at the end of the line. If the system displays any exit codes displayed on the Java entries, that process is not running. Escalate the problem to Avaya Technical Support. The id=aut and id=schd only displays when you have installed the Historical subsystem. The recorder entries display only if you are collecting data from CMS or Avaya IC. Forwarder entries might display on a server that you have installed the Real-time subsystem. 5. If OA is not running (mom is not active), enter: pa start all 6. Repeat Step 4 to verify that OA has started. 7. If you are not successful starting OA, see Avaya Operational Analyst Release 7.3.x Maintenance and Troubleshooting Guide for more troubleshooting information. Installation and Configuration February

256 Chapter 5: Making changes to installed Avaya OA components 8. Enter: oalist The system displays a message similar to the following: Subsystems installed Historical Real Time Reports Data API Utility Source-EC Server Names Historical: puoaaix7205 Historical Database: <IP_Address_of_Historical_Database_System> Database information Type: DB2 AdminID: db2inst1 UserID: db2inst1 Instance Name: db2inst1 Port Number: OA DB Name: girish OA DB Schema Name: oaschema IC UserID: repository IC Repository DB Name: repository Using a Backend/Remote Database IC Historical Tables created DB2 Path: /home/db2inst1 DB2 Library Path: /home/db2inst1/sqllib DB2 Version: 9.5.x User information OA User ID: biadmin Group ID: oaadmin Reports information Reports Group ID: oarpt Report Writer Group ID: oawriter Tomcat Home: /home/biadmin/bi/stumbras/tomcat Tomcat Port: 9080 OA Software information Version Installed: If you have installed the Historical subsystem, use the following commands and responses to verify that the required services are running. If the services are not running, escalate the problem using the normal channels. 256 Installation and Configuration February 2017

257 Adding Avaya OA components a. Enter the following command to determine if the Avaya Business Intelligence Service is running: ps -ef grep initsrv The system displays a message similar to the following: root Dec 27? 0:06 /opt/bi/bin/initsrv -n oaadmin -v 30 biadmin :28:00 pts/11 0:00 grep initsrv b. Enter the following command to determine if the ORBacus Naming Service is running: ps -ef grep naming The system displays a message similar to the following: biadmin Oct 21? 6:48 /export/home/biadmin/ jre<version_number>/bin/java -Dooc.naming.port=10000 com.ooc.cosn biadmin :27:35 pts/3 0:00 grep naming 10. If you have installed the Real-time subsystem, use the following commands and responses to verify that the required services are running. If the services are not running, escalate the problem using the normal channels. a. Enter the following command to determine if the Avaya Business Intelligence Service is running: ps -ef grep initsrv The system displays a message similar to the following: root Dec 27? 0:06 /opt/bi/bin/initsrv -n oaadmin -v 30 biadmin :28:00 pts/11 0:00 grep initsrv b. Enter the following command to determine if the ORBacus Naming Service is running: ps -ef grep naming The system displays a message similar to the following: biadmin Oct 21? 6:48 /export/home/biadmin/ jre<version_number>/bin/java -Dooc.naming.port=10000 com.ooc.cosn biadmin :27:35 pts/3 0:00 grep naming Installation and Configuration February

258 Chapter 5: Making changes to installed Avaya OA components c. Enter the following command to determine if the TimesTen Data Manager is running: ps -ef grep timesten The system displays a message similar to the following: biadmin :01:34 pts/0 0:00 grep timesten root Apr 16-0:17 /home/biadmin/timesten5.1.34/ TimesTen/avaya_bi/bin/timestensubd -verbose -id 2 -facility user root Apr 16-0:17 /home/biadmin/timesten5.1.34/ TimesTen/avaya_bi/bin/timestensubd -verbose -id 1 -facility user root Apr 16-3:35 /home/biadmin/timesten5.1.34/ TimesTen/avaya_bi/bin/timestensubd -verbose -id 3 -facility user root Apr 16-0:42 /home/biadmin/timesten5.1.34/ TimesTen/avaya_bi/bin/timestend -fg root Apr 16-0:18 /home/biadmin/timesten5.1.34/ TimesTen/avaya_bi/bin/timestensubd -verbose -id 0 -facility user 11. If you have installed the Source-EC subsystem, use the following commands and responses to verify that the required services are running. If the services are not running, escalate the problem using the normal channels. a. Enter the following command to determine if the ORBacus Naming Service is running: ps -ef grep naming The system displays a message similar to the following: biadmin Oct 21? 6:48 /export/home/biadmin/ jre<version_number>/bin/java -Dooc.naming.port=10000 com.ooc.cosn biadmin :27:35 pts/3 0:00 grep naming 12. If you have installed the Report subsystem, enter the following commands to stop and restart the Tomcat software:. /opt/bi/.profile cd /opt/bi/stumbras/tomcat/bin For OA and earlier:./shutdown.sh./startup.sh For OA and later:./stopoareport.sh./startoareport.sh 13. If you have installed the Report subsystem, use the following commands and responses to verify that the required services are running. If the services are not running, escalate the problem using the normal channels. 258 Installation and Configuration February 2017

259 Adding Avaya OA components a. Enter the following command to determine if the Avaya Business Intelligence Service is running: ps -ef grep initsrv The system displays a message similar to the following: root Dec 27? 0:06 /opt/bi/bin/initsrv -n oaadmin -v 30 biadmin :28:00 pts/11 0:00 grep initsrv b. Enter the following command to determine if the ORBacus Naming Service is running: ps -ef grep naming The system displays a message similar to the following: biadmin Oct 21? 6:48 /export/home/biadmin/ jre<version_number>/bin/java -Dooc.naming.port=10000 com.ooc.cosn biadmin :27:35 pts/3 0:00 grep naming c. Enter the following command to determine if Tomcat is running: ps -eaf grep catalina grep /opt/bi/stumbras/tomcat The system displays a message similar to the following: biadmin :27:59 pts/1 1:01 /home/biadmin/jre<version_number>/ bin/java -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager -Djava.util.l ogging.config.file=/opt/bi/stumbras/tomcat/conf/logging.properties -Djava.endors ed.dirs=/opt/bi/stumbras/tomcat/endorsed -classpath :/opt/bi/stumbras/tomcat/bin /bootstrap.jar -Dcatalina.base=/opt/BI/stumbras/tomcat -Dcatalina.home=/opt/BI/s tumbras/tomcat -Djava.io.tmpdir=/opt/BI/stumbras/tomcat/temp org.apache.catalina.startup.bootstrap start 14. To verify that OA reports are running using the Tomcat Administrative Console: a. In a browser window, enter: where report_server_fqdn is the fully qualified domain name of the server where you installed the Report subsystem. The port_number is the port number the system assigns to the Tomcat Administrative Console. For example, b. In the left pane, click Tomcat Manager. c. Log in to the Tomcat Administrative Console using the following login credentials: 1. UserID: admin 2. Password: admin Installation and Configuration February

260 Chapter 5: Making changes to installed Avaya OA components d. In the Tomcat Web Application Manager page, check for: Display Name Stumbras Running true Repairing Avaya OA components The repair process reinstalls software that was previously installed for components that are not working properly. When repairing a subsystem or a client software, many of the installation dialog box fields have data already populated from the original installation. This data you cannot change. This section includes the following topics: Considerations when doing a repair on page 260 Repairing Avaya OA components on page 261 Repairing Avaya OA components on the CMS server with RHEL platform on page 272 Completing a repair to Avaya OA software on page 276 Considerations when doing a repair When doing a repair, decide the following: During the repair process, the system does not repair some folders, and files because they have been previously changed during the running of OA. The components located under the %PABASE%\data or $PABASE/data folder are untouched. Therefore, you must have a valid backup of this area if file system problems develop. With the backup you restore these folders after the repair. Further, the repair process does not repair the contents of a Historical or Real-time database. The database administrator must resolve the problems with databases. After doing a repair of the Basic Report subsystem, you must go to each Report client system, remove the Report client, and reinstall the Report client. For more information, see Installing and testing the Report client on page Installation and Configuration February 2017

261 Repairing Avaya OA components Repairing Avaya OA components The procedures for repairing Avaya OA software is almost identical for all operating systems. For this procedure, the Windows dialog boxes displays and any differences for the other operating systems are described. To repair OA components: 1. Stop all OA processes. For more information, see Stopping or starting processes and services before making changes on page Do one of the following to access and start the installation executable: Installation and Configuration February

262 Chapter 5: Making changes to installed Avaya OA components CAUTION:! CAUTION: Install from a DVD drive that is local to the server where you are installing OA. Installing from a networked DVD drive is not supported. Operating System Windows Procedure 1. Log in with a user ID that has administration privileges. 2. If you have installed the Windows Terminal Services in Application mode, open a command prompt window and enter: change user /install CAUTION:! CAUTION: If you have installed the Windows Terminal Services in Administration mode, you cannot properly install any OA subsystem on that system. For more information, see Avaya Operational Analyst Release 7.3.x Installation Planning and Prerequisites. 3. Put the OA DVD in the drive. 4. Using Windows Explorer, navigate to the DVD drive and double-click the WinSetup.exe file. 262 Installation and Configuration February 2017

263 Repairing Avaya OA components Operating System Solaris AIX Procedure 1. Log in as root. 2. Put the OA DVD in the drive and wait about 15 seconds. A file manager window displays the contents of the DVD. If the File Manager window does not open, enter the following commands to start the volume manager: /etc/init.d/volmgt stop /etc/init.d/volmgt start 3. From a terminal window, enter the following commands:. /opt/bi/.profile cd /cdrom/cdrom0./solsetup 1. Log in as root. 2. To set the monitor display, enter: export DISPLAY=hostname:0.0 where hostname is the name of the server. 3. If you are adding the Historical subsystem, enter the following commands to set the DB2 environment: - As the instance owner, or any member of DB2 SYSADM group: export EXTSHM=ON db2set DB2ENVLIST=EXTSHM db2stop db2start - As the user launching the OA Installation (root): # export EXTSHM=ON #./AixSetup 4. Put the OA DVD in the drive and wait about 15 seconds.. /opt/bi/.profile mkdir /cdrom (if this folder does not already exist) mount -v cdrfs -r /dev/cd0 /cdrom cd /cdrom./aixsetup Installation and Configuration February

264 Chapter 5: Making changes to installed Avaya OA components After several seconds, the Initializing wizard window displays, followed by the Welcome dialog box. Important:! Important: You can stop the installation any time by clicking Cancel before you run the actual installation of files (see Step 27). If you click Cancel, you are asked to confirm your intention to cancel. If you cancel, the installation is terminated and the system is restored to its previous state. 3. Click Next. The License Key dialog box displays. 4. Enter the provided license key for the components purchased. 5. Click Next. The License Agreement dialog box displays. 6. Select I accept the terms in the license agreement. 7. Click Next. The User Information dialog box displays. The Domain field only displays for Windows systems. 8. Enter User password and Confirm password for the installed user ID. 9. Click Next. 264 Installation and Configuration February 2017

265 Repairing Avaya OA components There might be a long delay before the next dialog box displays. The Feature Selection dialog box displays the components that were previously installed. In this example, all available components are installed. 10. Select the components to repair. Installation and Configuration February

266 Chapter 5: Making changes to installed Avaya OA components Important:! Important: After selecting or clearing a check box, there might be a delay before the dialog box refreshes and you see the check mark or the check mark is cleared. This delay might take a few seconds. Do not select or clear another check box until the dialog box refreshes and you can see that the check box is select or clear. You can only select components that are already installed. To install a new component, see the procedure Adding Avaya OA components on page 215. The following example shows the Feature Selection dialog box with the Historical subsystem, Reporting subsystem, Data API Utility, and Administration client selected for repair: 11. Click Next. One of the following occurs: If you are repairing the Historical subsystem or the Report subsystem on a Windows or Solaris system, the Reports Configuration dialog box displays, but you cannot change any options. Continue with Step 12. If you are repairing the Report subsystem on an AIX system, and the Report subsystem was previously installed using a non default Tomcat Administrative Console user ID, the Reports Configuration dialog box displays the current Tomcat Admin Console User ID. The user ID password must be entered and confirmed. Continue with Step 12. If you are not repairing the Historical subsystem or the Report subsystem, the process continues with Step Click Next. 266 Installation and Configuration February 2017

267 Repairing Avaya OA components 13. If you are repairing the Historical subsystem, the Historical Server Configuration dialog box displays. If you are not repairing the Historical subsystem, continue with Step Perform the following: If you must add a new data collection source, select that source, either IC or CMS. If you are repairing an existing data collection source, do not select a new source. Complete the Alarm Services options as needed. The server name must be the server where you installed the Source-EC subsystem. The system might display this information, but you can change the information if needed. 15. Click Next. 16. One of the following occurs: If you are repairing only the Source-CMS subsystem on a Solaris or RHEL server, the CMS User ID dialog box displays. You must enter and confirm the password for the Informix user ID. Continue with Step 25. If you are repairing only the Real-time subsystem, continue with Step 23. Installation and Configuration February

268 Chapter 5: Making changes to installed Avaya OA components If you are repairing the Historical subsystem, continue with Step. The Database Configuration dialog box displays. You can only change the password fields. 17. Enter and confirm the administrator password. If during the repair you are adding Avaya IC as a data collection source, enter the IC DB User ID, IC DB User Password, and IC Repository Database name. 18. Click Next. A warning message might display. 19. Click OK to acknowledge the warning. 268 Installation and Configuration February 2017

269 Repairing Avaya OA components There might be a long delay before the next dialog box displays. The following dialog box displays when using Microsoft SQL Server. If you are not using Microsoft SQL, continue with Step Select Use Existing DB to use an existing database. 21. If you choose to not use the existing database, enter the size and location of the Microsoft SQL Server Transaction Log. You can use the default locations if you want. 22. Click Next. Installation and Configuration February

270 Chapter 5: Making changes to installed Avaya OA components 23. If you are repairing the Real-time subsystem, the Real-time Database dialog box displays, but you cannot change any options. If you are not repairing the Real-time subsystem, continue with Step 25. CAUTION: 24. Click Next. There might be a long delay before the next dialog box displays. 25. The system displays the Installation Preview dialog box listing the components you have selected. 26. Scroll through the preview dialog box to verify the selected components and the configuration data.! CAUTION: Do not close the Progress dialog box after you have clicked Next in the following step. If you close the Progress dialog box after starting the installation, you disrupt the installation. You must contact Avaya support to do a manual cleanup of the installation. 27. Click Next to start the installation. The Progress dialog box displays the progress of the installation, which takes several minutes. Near the end of the installation, the dialog box goes blank for some time. When the installation is complete, the Install Complete dialog box displays. 28. Click Next. On Solaris and AIX, the Install Complete dialog box closes and the repair is complete. 270 Installation and Configuration February 2017

271 Repairing Avaya OA components Important: On Windows, the Restart System dialog box displays. Before you restart the server, ensure that you save a copy of the server.properties file if the file is deleted during the restart. Perform the following: 1. Open Windows Explorer. 2. Navigate to %PABASE%\BI\data\admin. 3. Copy the server.properties file onto the Windows clipboard. 4. Go to your Windows desktop or some other location other than the OA installation folder. Then paste the server.properties file there.! Important: You must always restart a Windows server for OA to operate properly. If the system does not request to restart the server, you must manually restart the server. 5. Return to the Restart System dialog box, select the option to restart your system now, and click Next. 6. After the system restarts, navigate to %PABASE%\BI\data\admin. 7. Verify that the server.properties file is in the folder. 8. If the file is not in the folder, go to the location where you saved a copy of server.properties and copy the file onto the Windows clipboard. 9. Navigate to %PABASE%\BI\data\admin. 10. Paste the server.properties file into the folder. 29. Do one of the following: On Windows, press the eject button on the DVD drive, remove the DVD, and store it in a safe location. On Solaris, close all, but one terminal window and enter: cd / eject cdrom On AIX, close all, but one terminal window and enter: cd / umount /cdrom 30. Press the eject button on the DVD drive (AIX only), remove the OA DVD, and store it in a safe location. Installation and Configuration February

272 Chapter 5: Making changes to installed Avaya OA components Repairing Avaya OA components on the CMS server with RHEL platform To repair OA components: 1. Stop all OA processes. See Stopping or starting processes and services before making changes on page Change the folder to the location from where you want to install Avaya OA components. CAUTION:! CAUTION: Install from a CD/DVD drive that is local to the server where you are installing OA. Installing from a networked DVD drive is not supported. After several seconds, the Initializing wizard window displays, followed by the Welcome dialog box. Important:! Important: You can stop the installation any time by clicking Cancel before you run the actual installation of files. If you click Cancel, you are asked to confirm your intention to cancel. If you cancel, the system stops the installation and restores the system to the previous state. 3. From a terminal window, enter the following commands:./linsetup 4. Click Next. The License Key dialog box displays. 5. Enter the provided license key for the components purchased. 6. Click Next. The License Agreement dialog box displays. 7. Select I accept the terms in the license agreement. 272 Installation and Configuration February 2017

273 Repairing Avaya OA components 8. Click Next. The User Information dialog box displays. 9. Enter User password and Confirm password for the installed user ID. 10. Click Next. The Feature Selection dialog box displays. This dialog box indicates the components that were previously installed. In this example, the Source - CMS Subsystem and Data API Utility components are already installed. Installation and Configuration February

274 Chapter 5: Making changes to installed Avaya OA components Important: 11. Select the components to repair.! Important: After selecting or clearing a check box, there might be a delay before the dialog box refreshes and you see the check mark or the check mark is cleared. This delay might take a few seconds. Do not select or clear another check box until the dialog box refreshes and you can see that the check box is select or clear. 12. Click Next. The Historical Server Configuration dialog box displays. 13. Click Next. There might be a long delay before the next dialog box displays. 274 Installation and Configuration February 2017

275 Repairing Avaya OA components 14. Click Next. The system displays the dialog box for specifying the CMS password. CAUTION: 15. Click Next. The system displays the Installation Preview dialog box listing the components you have selected. 16. Scroll through the preview dialog box to verify the selected components and the configuration data.! CAUTION: Do not close the Progress dialog box after you have clicked Next in the following step. If you close the Progress dialog box after the installation has started, the installation will be disrupted and you must contact Avaya support to do a manual cleanup of the installation. 17. Click Next to start the installation. The Progress dialog box displays the progress of the installation, which takes several minutes. Near the end of the installation, the dialog box goes blank for some time. When the installation is complete, the Install Complete dialog box displays. 18. Click Next. 19. If you are installing the software from the CD/DVD, close all, but one terminal window and enter: cd / eject cdrom 20. Remove the Avaya OA CD/DVD. Installation and Configuration February

276 Chapter 5: Making changes to installed Avaya OA components Completing a repair to Avaya OA software Depending on the platform you are using, use the procedures in the following sections to complete your repair: To complete a repair to a Windows system on page 276 To complete a repair to a Solaris system on page 279 To complete a repair to the RHEL system on page 285 To complete a repair to an AIX system on page 287 To complete a repair to a Windows system 1. Log in using an OA user ID and password. For more information, see Avaya Operational Analyst Release 7.3.x Installation Planning and Prerequisites. 2. Open a command prompt window. 3. If Terminal Services is enabled, enter: change user /execute 4. In the command prompt window, enter the following command to show what processes are running: pa list The system displays a message similar to the following:. system boot Dec 20 07:54. run-level 4 Dec 31 10:23 4 java. Dec 20 07: id=admb java. Dec 20 07: id=adm0 java. Jan 02 16: id=ams java. Dec 20 07: id=aut java. Dec 20 07: id=schd... There can be several Java entries, and these lines cannot have an exit code at the end of the line. If the system displays any exit codes on the Java entries, that process is not running. Escalate the problem to Avaya Technical Support. The id=aut and id=schd only displays when you have installed the Historical subsystem. 276 Installation and Configuration February 2017

277 Repairing Avaya OA components The recorder entries displays only if you are collecting data from CMS or Avaya IC. Forwarder entries might display on a server which you have installed the Real-time subsystem. 5. If you get the message mom is not active, enter: pa start all 6. Repeat Step 4 to verify that OA has started. Installation and Configuration February

278 Chapter 5: Making changes to installed Avaya OA components 7. Enter: oalist The system displays a message similar to the following: Subsystems installed Historical Real Time Reports Data API Utility Source-EC Advanced Reports Administration Client Server Names Historical: punoasvorsr03 Historical Database: Database information Type: MSSQL AdminID: sa UserID: oadba Instance Name: MSSQLSERVER Port Number: 1433 OA DB Name: oadb IC UserID: repository IC Repository DB Name: repository Using a Backend/Remote Database IC Historical Tables created User information OA User ID: biadmin Domain: punoadom Group ID: oaadmin Active Directory Server or Localhost Information ADS Version: 3 ADS Port: 389 ADS Admin Group: CN=oaadmin,OU=OA Admins,DC=punoadom,DC=avaya,DC=com ADS Report Group: CN=oarpt,OU=OA Admins,DC=punoadom,DC=avaya,DC=com ADS Report Writer Group: CN=oawriter,OU=OA Admins,DC=punoadom,DC=avaya,DC=com Admin Client Locale Admin Client Locale: en_us OA Software information Version Installed: Select Start > Programs > Administrative Tools > Services. 278 Installation and Configuration February 2017

279 Repairing Avaya OA components 9. Validate that the following services are running and are set to run automatically. If these services are not administered to run automatically, administer these services as such. If you have installed the Historical subsystem, check for the following: - Avaya Business Intelligence Service - ORBacus Naming Service If you have installed the Real-time subsystem, check for the following: - Avaya Business Intelligence Service - ORBacus Naming Service - TimesTen Data Manager If you have installed the Report subsystem, check for the following: - Avaya Business Intelligence Service - ORBacus Naming Service - Tomcat service - Stumbras-Tomcat (For OA and earlier) - Avaya OA Reporting Application (For OA and later) If you have installed the Source-EC subsystem, check for the following: - ORBacus Naming Service 10. If you are not successful starting OA, see Avaya Operational Analyst Release 7.3.x Maintenance and Troubleshooting Guide for more troubleshooting information. To complete a repair to a Solaris system CAUTION: 1. Log out of the desktop environment. 2. Log in using an OA user ID and password. For more information, see Avaya Operational Analyst Release 7.3.x Installation Planning and Prerequisites.! CAUTION: Do not use any OA commands while logged in as root. Using the root login ID on these commands changes ownership of files and makes them unusable by the OA user ID. 3. Enter:. /opt/bi/.profile Installation and Configuration February

280 Chapter 5: Making changes to installed Avaya OA components 4. Enter the following command to determine what processes are running: pa list The system displays a message similar to the following:. system boot Dec 20 07:54. run-level 4 Dec 31 10:23 4 java. Dec 20 07: id=admb java. Dec 20 07: id=adm0 java. Jan 02 16: id=ams java. Dec 20 07: id=aut java. Dec 20 07: id=schd There can be several Java entries, and these lines cannot have an exit code at the end of the line. If the system displays any exit codes on the Java entries, that process is not running. Escalate the problem to Avaya Technical Support. The id=aut and id=schd only displays when you have installed the Historical subsystem. The recorder entries display only if you are collecting data from CMS or Avaya IC. Forwarder entries might display on a server that you have installed the Real-time subsystem. 5. If you get the message mom is not active, enter: pa start all 6. Repeat Step 4 to verify that OA has started. 7. If you are not successful starting OA, see Avaya Operational Analyst Release 7.3.x Maintenance and Troubleshooting Guide or more troubleshooting information. 280 Installation and Configuration February 2017

281 Repairing Avaya OA components 8. Enter: oalist The system displays a message similar to the following: Subsystems installed Historical Real Time Reports Data API Utility Source-EC Server Names Historical: puoadvsolsr14 Historical Database: <IP_Address_of_Historical_Database_System> Reports: puoadvsolsr14 Database information Type: ORACLE AdminID: sys UserID: oadba Instance Name: oa7211g Port Number: 1521 IC UserID: repository Using a Backend/Remote Database IC Historical Tables created User information OA User ID: biadmin Group ID: oaadmin Reports information Reports Group ID: oarpt Report Writer Group ID: oawriter Tomcat Home: /export/home/biadmin/bi/stumbras/tomcat Tomcat Port: 9080 OA Software information Version Installed: If you have installed the Historical subsystem, use the following commands and responses to verify that the required services are running. If the services are not running, escalate the problem using the normal channels. a. Enter the following command to determine if the Avaya Business Intelligence Service is running: ps -ef grep initsrv The system displays a message similar to the following: root Dec 27? 0:06 /opt/bi/bin/initsrv -n oaadmin -v 30 biadmin :28:00 pts/11 0:00 grep initsrv Installation and Configuration February

282 Chapter 5: Making changes to installed Avaya OA components b. Enter the following command to determine if the ORBacus Naming Service is running: ps -ef grep naming The system displays a message similar to the following: biadmin Oct 21? 6:48 /export/home/biadmin/ jre<version_number>/bin/java -Dooc.naming.port=10000 com.ooc.cosn biadmin :27:35 pts/3 0:00 grep naming 10. If you have installed the Real-time subsystem, use the following commands and responses to verify that the required services are running. If the services are not running, escalate the problem using the normal channels. a. Enter the following command to determine if the Avaya Business Intelligence Service is running: ps -ef grep initsrv The system displays a message similar to the following: root Dec 27? 0:06 /opt/bi/bin/initsrv -n oaadmin -v 30 biadmin :28:00 pts/11 0:00 grep initsrv b. Enter the following command to determine if the ORBacus Naming Service is running: ps -ef grep naming The system displays a message similar to the following: biadmin Oct 21? 6:48 /export/home/biadmin/ jre<version_number>/bin/java -Dooc.naming.port=10000 com.ooc.cosn biadmin :27:35 pts/3 0:00 grep naming c. Enter the following command to determine if the TimesTen Data Manager is running: ps -ef grep timesten The system displays a message similar to the following: root Dec 23? 0:01 /export/home/biadmin/timesten5.1.34/ TimesTen/avaya_bi/bin/timestend root Dec 23? 0:00 /export/home/biadmin/timesten5.1.34/ TimesTen/avaya_bi/bin/timestensubd -id 0 root Dec 23? 0:00 /export/home/biadmin/timesten5.1.34/ TimesTen/avaya_bi/bin/timestensubd -id 1 root Dec 23? 0:00 /export/home/biadmin/timesten5.1.34/ TimesTen/avaya_bi/bin/timestensubd -id 2 root Dec 23? 0:00 /export/home/biadmin/timesten5.1.34/ TimesTen/avaya_bi/bin/timestensubd -id 3 biadmin :34:22 pts/11 0:00 grep timesten 282 Installation and Configuration February 2017

283 Repairing Avaya OA components 11. If you have installed the Report subsystem, use the following commands and responses to verify that the required services are running. If the services are not running, escalate the problem using the normal channels. a. Enter the following command to determine if the Avaya Business Intelligence Service is running: ps -ef grep initsrv The system displays a message similar to the following: root Jan 20? 0:06 /opt/bi/bin/initsrv -n oaadmin -v 30 biadmin :28:00 pts/11 0:00 grep initsrv b. Enter the following command to determine if the ORBacus Naming Service is running: ps -ef grep naming The system displays a message similar to the following: biadmin Jan 20? 6:48 /export/home/biadmin/ jre<version_number>/bin/java -Dooc.naming.port=10000 com.ooc.cosn biadmin :27:35 pts/3 0:00 grep naming 12. If you have installed the Source-CMS subsystem, use the following command and response to verify that the required service is running. If the service is not running, escalate the problem using the normal channels. ps -ef grep naming The system displays a message similar to the following: biadmin Oct 21? 6:48 /export/home/biadmin/ jre<version_number>/bin/java -Dooc.naming.port=10000 com.ooc.cosn biadmin :27:35 pts/3 0:00 grep naming 13. If you have installed the Source-EC subsystem, use the following commands and responses to verify that the required services are running. If the services are not running, escalate the problem using the normal channels. a. Enter the following command to determine if the ORBacus Naming Service is running: ps -ef grep naming The system displays a message similar to the following: biadmin Oct 21? 6:48 /export/home/biadmin/ jre<version_number>/bin/java -Dooc.naming.port=10000 com.ooc.cosn biadmin :27:35 pts/3 0:00 grep naming 14. Start the Tomcat server after you configure the Admin client. For more information, see Administration client options on page 168. Installation and Configuration February

284 Chapter 5: Making changes to installed Avaya OA components CAUTION: a. Log in to the Solaris system using an Avaya OA user ID and password. For more information, see Avaya Operational Analyst Release 7.3.x Installation Planning and Prerequisites.! CAUTION: Do not use any Avaya OA commands while logged in as root. Using the root login ID on these commands changes ownership of files and makes them unusable by the Avaya OA user ID. b. Enter the command:./opt/bi/.profile. c. Go to the Tomcat server location. Enter the command: cd /opt/bi/stumbras/tomcat/bin. d. Start the Tomcat server. Enter the command: For OA and earlier:./startup.sh For OA and later:./startoareport.sh 15. Check the Tomcat server logs to verify that Tomcat is running successfully. a. Go to the $PABASE/stumbras/tomcat/logs/ folder. b. Enter the command: vi catalina.out 16. Check if the Tomcat server is running successfully. a. Go to the $PABASE/stumbras/tomcat/conf folder. b. Check if the PID.txt file is present in the folder. The PID.txt file indicates that the process ID of the Tomcat server is registered in the PID.txt file. 17. Stop the Tomcat server. a. Enter the command:./opt/bi/.profile. b. Go to the Tomcat server location. Enter the command: cd /opt/bi/stumbras/tomcat/bin. 284 Installation and Configuration February 2017

285 Repairing Avaya OA components c. Stop the Tomcat server. Enter the command: For OA and earlier:./shutdown.sh -force For OA and later:./stopoareport.sh -force To complete a repair to the RHEL system 1. Log out of the desktop environment. 2. Log in to the system using an Avaya OA user ID and password. For more information, see Avaya Operational Analyst Release 7.3.x Installation Planning and Prerequisites. CAUTION:! CAUTION: Do not use any Avaya OA commands while logged in as root. Using the root login ID on these commands changes ownership of files and makes them unusable by the Avaya OA user ID. 3. Enter:. /opt/bi/.profile 4. Enter the following command to determine if the Avaya Business Intelligence Service is running: ps -ef grep initsrv The system displays a message similar to the following: root :12? 00:00:00 /opt/bi/bin/initsrv -n oaadmin -v Enter the following command to determine if the ORBacus Naming Service is running: ps -ef grep CosNaming The system displays a message similar to the following: root :12? 00:00:00 /export/home/biadmin/ jre<version_number>/bin/java com.ooc.cosnaming.server -IIOPport Installation and Configuration February

286 Chapter 5: Making changes to installed Avaya OA components 6. Enter the following command to determine what processes are running: pa list The system displays a message similar to the following: (cmsjune74)-(root)=# pa list all. system boot Oct 1 17:13. run-level 4 Oct 1 17:13 4 java. Oct 1 17:13 old id=admb java. Oct 1 17:13 old id=adm0 java. Oct 1 17:13 old id=ams There can be several Java entries, and these lines cannot have an exit code at the end of the line. If the system displays any exit codes on the Java entries, that process is not running. Escalate the problem to Avaya Technical Support. The id=aut and id=schd only displays when you have installed the Historical subsystem. The recorder entries displays only if you are collecting data from CMS or Avaya IC. Forwarder entries might display on a server that you have installed the Real-time subsystem. 7. If you get the message mom is not active, enter: pa start all 8. Repeat Step 4 to verify Avaya OA is running. If you are not successful starting Avaya OA, see Avaya Operational Analyst Release 7.3.x Maintenance and Troubleshooting Guide for more troubleshooting information. 286 Installation and Configuration February 2017

287 Repairing Avaya OA components 9. Enter the following command: oalist The system displays a message similar to the following: Subsystems installed Data API Utility Source-CMS Server Names Historical: icdev84 Database information Type: UNSET User information CMS ID: informix OA User ID: biadmin Group ID: oaadmin OA Software information Version Installed: To complete a repair to an AIX system 1. Log out of the desktop environment. 2. Log in using an OA user ID and password. For more information, see Avaya Operational Analyst Release 7.3.x Installation Planning and Prerequisites. CAUTION:! CAUTION: Do not use any OA commands while logged in as root. Using the root login ID on these commands changes ownership of files and makes them unusable by the OA user ID. 3. Enter:. /opt/bi/.profile Installation and Configuration February

288 Chapter 5: Making changes to installed Avaya OA components 4. Enter the following command to determine what processes are running: pa list The system displays a message similar to the following:. system boot Dec 20 07:54. run-level 4 Dec 31 10:23 4 java. Dec 20 07: id=admb java. Dec 20 07: id=adm0 java. Jan 02 16: id=ams java. Dec 20 07: id=aut java. Dec 20 07: id=schd... There can be several Java entries, and these lines cannot have an exit code at the end of the line. If the system displays any exit codes on the Java entries, that process is not running. Escalate the problem to Avaya Technical Support. The id=aut and id=schd only displays when you have installed the Historical subsystem. The recorder entries display only if you are collecting data from CMS or Avaya IC. Forwarder entries might display on a server that you have installed the Real-time subsystem. 5. If OA is not running (mom is not active), enter: pa start all 6. Repeat Step 4 to verify that OA has started. 7. If you are not successful starting OA, see Avaya Operational Analyst Release 7.3.x Maintenance and Troubleshooting Guide for more troubleshooting information. 288 Installation and Configuration February 2017

289 Repairing Avaya OA components 8. Enter: oalist The system displays a message similar to the following: Subsystems installed Historical Real Time Reports Data API Utility Source-EC Server Names Historical: puoaaix7205 Historical Database: <IP_Address_of_Historical_Database_System> Database information Type: DB2 AdminID: db2inst1 UserID: db2inst1 Instance Name: db2inst1 Port Number: OA DB Name: girish OA DB Schema Name: oaschema IC UserID: repository IC Repository DB Name: repository Using a Backend/Remote Database IC Historical Tables created DB2 Path: /home/db2inst1 DB2 Library Path: /home/db2inst1/sqllib DB2 Version: 9.5.x User information OA User ID: biadmin Group ID: oaadmin Reports information Reports Group ID: oarpt Report Writer Group ID: oawriter Tomcat Home: /home/biadmin/bi/stumbras/tomcat Tomcat Port: 9080 OA Software information Version Installed: If you have installed the Historical subsystem, use the following commands and responses to verify that the required services are running. If the services are not running, escalate the problem using the normal channels. Installation and Configuration February

290 Chapter 5: Making changes to installed Avaya OA components a. Enter the following command to determine if the Avaya Business Intelligence Service is running: ps -ef grep initsrv The system displays a message similar to the following: root Dec 27? 0:06 /opt/bi/bin/initsrv -n oaadmin -v 30 biadmin :28:00 pts/11 0:00 grep initsrv b. Enter the following command to determine if the ORBacus Naming Service is running: ps -ef grep naming The system displays a message similar to the following: biadmin Oct 21? 6:48 /export/home/biadmin/ jre<version_number>/bin/java -Dooc.naming.port=10000 com.ooc.cosn biadmin :27:35 pts/3 0:00 grep naming 10. If you have installed the Real-time subsystem, use the following commands and responses to verify that the required services are running. If the services are not running, escalate the problem using the normal channels. a. Enter the following command to determine if the Avaya Business Intelligence Service is running: ps -ef grep initsrv The system displays a message similar to the following: root Dec 27? 0:06 /opt/bi/bin/initsrv -n oaadmin -v 30 biadmin :28:00 pts/11 0:00 grep initsrv b. Enter the following command to determine if the ORBacus Naming Service is running: ps -ef grep naming The system displays a message similar to the following: biadmin Oct 21? 6:48 /export/home/biadmin/ jre<version_number>/bin/java -Dooc.naming.port=10000 com.ooc.cosn biadmin :27:35 pts/3 0:00 grep naming 290 Installation and Configuration February 2017

291 Repairing Avaya OA components c. Enter the following command to determine if the TimesTen Data Manager is running: ps -ef grep timesten The system displays a message similar to the following: biadmin :01:34 pts/0 0:00 grep timesten root Apr 16-0:17 /home/biadmin/timesten5.1.34/ TimesTen/avaya_bi/bin/timestensubd -verbose -id 2 -facility user root Apr 16-0:17 /home/biadmin/timesten5.1.34/ TimesTen/avaya_bi/bin/timestensubd -verbose -id 1 -facility user root Apr 16-3:35 /home/biadmin/timesten5.1.34/ TimesTen/avaya_bi/bin/timestensubd -verbose -id 3 -facility user root Apr 16-0:42 /home/biadmin/timesten5.1.34/ TimesTen/avaya_bi/bin/timestend -fg root Apr 16-0:18 /home/biadmin/timesten5.1.34/ TimesTen/avaya_bi/bin/timestensubd -verbose -id 0 -facility user 11. If you have installed the Source-EC subsystem, use the following commands and responses to verify that the required services are running. If the services are not running, escalate the problem using the normal channels. a. Enter the following command to determine if the ORBacus Naming Service is running: ps -ef grep naming The system displays a message similar to the following: biadmin Oct 21? 6:48 /export/home/biadmin/ jre<version_number>/bin/java -Dooc.naming.port=10000 com.ooc.cosn biadmin :27:35 pts/3 0:00 grep naming 12. If you have installed the Report subsystem, enter the following commands to stop and restart the Tomcat software:. /opt/bi/.profile cd /opt/bi/stumbras/tomcat/bin For OA and earlier:./shutdown.sh./startup.sh For OA and later:./stopoareport.sh./startoareport.sh 13. If you have installed the Report subsystem, use the following commands and responses to verify that the required services are running. If the services are not running, escalate the problem using the normal channels. Installation and Configuration February

292 Chapter 5: Making changes to installed Avaya OA components a. Enter the following command to determine if the Avaya Business Intelligence Service is running: ps -ef grep initsrv The system displays a message similar to the following: root Dec 27? 0:06 /opt/bi/bin/initsrv -n oaadmin -v 30 biadmin :28:00 pts/11 0:00 grep initsrv b. Enter the following command to determine if the ORBacus Naming Service is running: ps -ef grep naming The system displays a message similar to the following: biadmin Oct 21? 6:48 /export/home/biadmin/ jre<version_number>/bin/java -Dooc.naming.port=10000 com.ooc.cosn biadmin :27:35 pts/3 0:00 grep naming c. Enter the following command to determine if Tomcat is running: ps -eaf grep catalina grep /opt/bi/stumbras/tomcat The system displays a message similar to the following: biadmin :27:59 pts/1 1:01 /home/biadmin/jre<version_number>/ bin/java -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager -Djava.util.l ogging.config.file=/opt/bi/stumbras/tomcat/conf/logging.properties -Djava.endors ed.dirs=/opt/bi/stumbras/tomcat/endorsed -classpath :/opt/bi/stumbras/tomcat/bin /bootstrap.jar -Dcatalina.base=/opt/BI/stumbras/tomcat -Dcatalina.home=/opt/BI/s tumbras/tomcat -Djava.io.tmpdir=/opt/BI/stumbras/tomcat/temp org.apache.catalina.startup.bootstrap start 14. To verify that OA reports are running using the Tomcat Administrative Console: a. In a browser window, enter: where report_server_fqdn is the fully qualified domain name of the server where you have installed the Report subsystem. The port_number is the port number the system assigns to the Tomcat Administrative Console. For example, b. In the left pane, click Tomcat Manager. c. Log in to the Tomcat Administrative Console using the following login credentials: 1. UserID: admin 2. Password: admin 292 Installation and Configuration February 2017

293 Moving subsystems d. In the Tomcat Web Application Manager page, check for: Display Name Stumbras Running true Moving subsystems You might find that you must move subsystems between servers. Some examples of situations that might require moving subsystems include the following: You must replace an existing system in the OA configuration with a faster system to handle more traffic or more users. A single server OA configuration must expand to accommodate more traffic or more users. You move one or more of the OA subsystems from the server to another system. For more information, see Example of moving subsystems on page 294. You might replace a system because of a hardware failure. You might consolidate multiple CMS systems into one CMS system. The network is changing so that the fully qualified domain name for one or more systems changes. For more information, see Example for changing a domain name on page 302. As a prerequisite, you must set up TCP/IP and Domain Name Service (DNS) administration for each system in an OA configuration. For more information, see Avaya Operational Analyst Release 7.3.x Installation Planning and Prerequisites. This section includes the following topics: General guidelines on page 294 Example of moving subsystems on page 294 Moving the Real-time subsystem on page 295 Moving the Event Collector subsystem on page 297 Moving the Event Collector Bridge subsystem on page 297 Moving CMS and ACD subsystems on page 298 Moving the Report subsystem on page 300 Installation and Configuration February

294 Chapter 5: Making changes to installed Avaya OA components General guidelines Follow these general guidelines when moving subsystems: Install no more than one of the same type of subsystem on a physical system. For example there can only be one Historical, one Real-time, one Report, or one CMS subsystem for each system. Some subsystems can be co resident. CMS is the only subsystem that must reside on a separate physical system from the other subsystems. Choose a low traffic or no traffic time to move subsystem. Many subsystem changes require significant changes in data flow. Moving the Historical database is not supported. Doing so impacts a significant amount of OA and Avaya IC administration. Moving the Historical subsystem is not supported. Because Real-time data is transient, you can install the Real-time subsystem on a new system. This subsystem installation also installs the Real-time database on that system. The system forces an administration copy from Avaya IC to OA. Change Avaya IC to point to the new Real-time subsystem, and the data flows from Avaya IC to the new system. For more information, see Moving the Real-time subsystem on page 295. Communication between the Historical subsystem and any of the subsystems containing interfaces might fail because of an error. For example, network connectivity or the OA not running on the subsystem with the interfaces. Trying to delete or move those subsystems results in an Admin Client error message. You must stop the process of deletion or movement of the subsystem. You must work to re-establish the communication before proceeding to move or delete the subsystem. Trying to go ahead with the deletion or movement of the subsystem fails until you correct the problem. The Admin Client does not allow the deletion or movement to occur unless it accurately determines whether you have disabled the interface services before the deletion or movement occurs. Use the system console on the original server to stop the services. For more information, see Chapter 5: Making changes to installed Avaya OA components on page 207. Then remove the original subsystem, following the instructions in Removing Avaya OA components on page 312. Example of moving subsystems The following example shows how you can take a single-server OA configuration and move to a two-server configuration. In this example, assume that the following subsystems in a single server system are all on server A: Historical Real-time 294 Installation and Configuration February 2017

295 Moving subsystems Avaya IC Report If you move the Real-time and Report subsystems to server B: 1. Install the OA Real-time and Report subsystems on the new server, B. The standard OA installation program installs the software needed for these subsystems, including the Real-time database. 2. Move the Real-time subsystem. Follow the instructions in Moving the Real-time subsystem on page Move the Report subsystem. Follow the instructions in Moving the Report subsystem on page 300. Moving the Real-time subsystem Move an existing Real-time subsystem to another physical system by following these steps: 1. Install the OA Real-time subsystem software on the new server. For more information, see Installing Avaya OA components on page Stop all traffic from Avaya IC to OA by stopping the EC server in the IC Manager. 3. On the subsystem window of the Administration client, change the Real-time subsystem and change the location to be the domain name or IP address for the new system. The Administration client presents a list of any interface services that you must disable before proceeding. 4. Access the Interface Services window and select the services in the list. View the current status for each service, then disable each service. 5. Return to the subsystem window and then change the server location to that of the new system. 6. For each Avaya IC subsystem, click Modify... to verify that the Real-time subsystem drop-down box reflects the correct Real-time subsystem. 7. Access IC Manager and change the EC administration properties to point to the new Real-time system. 8. Using the IC Manager: Installation and Configuration February

296 Chapter 5: Making changes to installed Avaya OA components a. Select the Server tab. b. Select the EC that corresponds to the Real-time subsystem that you are moving. For example, the name is ECServer. c. Double-click to access the Server Editor dialog box. d. Select the Event Collector tab. e. Change the Data Manager Host name for the new Real-time server. f. Click Apply and click Ok. 296 Installation and Configuration February 2017

297 Moving subsystems 9. Return to the main IC Manager page and view the Services tab. Highlight the Event Collector Server to stop it and start it. Use the buttons with the red and green stoplights. The Avaya IC and new Real-time should be communicating at this point. Traffic can be restarted. The change in data flow forces a copy of administration data from the Avaya IC to OA when the new database comes up. 10. Remove the original subsystem. Follow the instructions specified in Removing Avaya OA components on page 312. Moving the Event Collector subsystem To move the Event Collector subsystem: 1. Install the Avaya IC software on the new server. For more information, see Avaya Interaction Center Release 7.3.x Installation and Configuration. 2. Install the Source-EC component on the new server. For more information, see Installing Avaya OA components on page On the new server, configure the EC so that EC properties, Data Manager Host, and Real-time System ID, are set correctly. For more information, see Determining Real-time System ID and Data Manager Host on page 184. The Data Manager Host should refer to the host for the Real-time subsystem. The Real-time System ID can match the Source ID for this Avaya IC subsystem in the OA Administration client. There are no changes in OA administration for Avaya IC. OA does not store location data (host name or the IP address) for the Avaya IC subsystem. In OA, Avaya IC exists as a logical subsystem with a source ID and an associated Real-time subsystem only. 4. Remove the original subsystem. Follow the instructions specified in Removing Avaya OA components on page 312. Moving the Event Collector Bridge subsystem You can move the EC Bridge subsystem only to a Windows server and to a server that has Business Advocate installed. To move the EC Bridge subsystem: 1. Install the Avaya IC software on the new server. For more information, see Avaya Interaction Center Release 7.3.x Installation and Configuration. Installation and Configuration February

298 Chapter 5: Making changes to installed Avaya OA components 2. Install the Source-EC Bridge component on the new server. For more information, see Installing Avaya OA components on a Windows platform on page On the new server, configure the EC Bridge so that the properties are set correctly. For more information, see Administering the Source-EC Bridge (Event Collector Bridge) on page 191. There are no changes in OA administration for Avaya IC. OA does not store location data (host name or IP address) for the Avaya IC subsystem. In OA, Avaya IC exists as a logical subsystem with a source ID and an associated Real-time subsystem only. 4. Remove the original subsystem. Follow the instructions specified in Removing Avaya OA components on page 312. Moving CMS and ACD subsystems When you move a CMS subsystem, you must also move the ACD subsystem that applies to that CMS server. This section includes the following topics: Moving a CMS subsystem on page 298 Moving ACDs associated with a CMS subsystem on page 299 Moving a CMS subsystem To move the CMS subsystem to a different CMS server: 1. Install the CMS subsystem on the new server (see Installing Avaya OA components on a CMS server - Solaris SPARC on page 117 and Installing Avaya OA components on a CMS server for RHEL on page 132). 2. On the subsystem window of the Administration client, highlight the CMS subsystem, and then click Modify? 3. Change the location (domain name or IP address) to location of the new system. The Administration client presents a list of interface services that you must disable before proceeding. 4. Access the Interface Services window and select the services in the list. Get the current status for each service and disable each service. Depending on the number of services and whether a forwarder or recorder is transferring data, disabling the services can take a long time. The Administration client might appear to stop responding during this procedure, but the client is working on the request. 5. Return to the subsystem window and then run the change of the location of the CMS. 298 Installation and Configuration February 2017

299 Moving subsystems 6. Enable the interface services on the new CMS. On the interface services window, select the CMS forwarders that reside on the new server and then click Enable. 7. Remove the original subsystem. Follow the instructions specified in Removing Avaya OA components on page 312. Do not use the above procedure to merge two CMS servers. Successful handling of CMS data requires that you retrieve all display names and create containers that use the desired display names. For example, assume CMS-A was collecting data from ACDs 1 and 2, and CMS-B was collecting data from ACDs 3 and 4. Now, the customer wants to use CMS-A to collect data for ACDs 1, 2, 3, and 4, and eliminate CMS-B. The user can configure CMS-A to add support for ACDs 3 and 4. Then the user can move those ACDs to CMS-A by accessing the Modify dialog box and changing the CMS Subsystem Name to be CMS-A. Finally, the user can delete CMS-B. 8. For each ACD that you move, schedule a data collection job to retrieve the display names: a. Access the scheduled jobs window. b. Select data collection from the Job Type drop-down list. Then click Add c. In the add dialog box, select the correct source subsystem and the Historical store of cms display names. Set the time parameters for the job so that it runs Now d. Click OK. e. Click Save. 9. On the Scheduled Jobs window, click Job Status. This displays the Job Status dialog box. 10. Select a Job Type of data collection and verify that the job has successfully completed. The job name can display in the table with a status of Successful. 11. Access the Container Profiles window to update or add any containers that can now include data for the new ACDs. 12. Remove the original subsystem. Follow the instructions specified in Removing Avaya OA components on page 312. Moving ACDs associated with a CMS subsystem Every ACD subsystem has an associated CMS subsystem name. To move an ACD, you must change the CMS subsystem name on the ACD subsystem dialog box. 1. On the subsystem window of the Administration client, highlight the ACD to be moved, and click Modify 2. Change the CMS Subsystem Name drop-down field to specify a different CMS. 3. Click OK. Installation and Configuration February

300 Chapter 5: Making changes to installed Avaya OA components 4. Click Save. The administration client returns a list of interface services that you must disable before you move the ACD. 5. Access the Interface Services window and highlight the interface services from the list. View status for each service, then highlight each service, and then click Disable. 6. Return to the subsystem window and then change the ACD again. 7. Change the CMS Subsystem Name. 8. Click OK. 9. Click Save. Forwarders now exist on the new CMS subsystem for that ACD. 10. Access the Interface Services window, and enable the forwarders to begin the data collection for the ACD. 11. Remove the original subsystem. Follow the instructions specified in Removing Avaya OA components on page 312. Moving the Report subsystem You can move a Report subsystem by either changing the location field in the subsystem dialog box, or by installing the new subsystem, adding the new subsystem, and then deleting the old subsystem. To move a Report subsystem by changing the location field in the subsystem dialog box: 1. Stop running reports on the server where you are removing the subsystem. 2. Install the Report subsystem on the new server using the OA installation DVD. For more information, see Installing Avaya OA components on page On the subsystem window of the Administration client, highlight the Report subsystem, and click Modify Change the location (domain name or IP address) to the name of the new system. 5. Click OK. 6. Click Save. 300 Installation and Configuration February 2017

301 Changing subsystem attributes Moving the Report subsystem changes the URL to the reports window. For example, if you had been using the URL the new URL can be if you moved the Report subsystem to system2. You must specify the port number 8999 in reports URL as Avaya OA 7.3.x bypasses IIS for Windows. For Example, 7. Remove the original subsystem. Follow the instructions specified in Removing Avaya OA components on page 312. To move a Report subsystem by installing the new subsystem, adding the new subsystem, and then deleting the old subsystem: 1. Stop running reports on the server where you are removing the subsystem. 2. Install the Report subsystem on the new server using the OA installation DVD. For more information, see Installing Avaya OA components on page Add the new Report subsystem. For more information, see Adding a Report subsystem on page 181. Moving the Report subsystem changes the URL to the reports window. For example, if you had been using the URL the new URL can be if you moved the Report subsystem to system2. You must specify the port number 8999 in reports URL as Avaya OA 7.3.x bypasses IIS for Windows. For Example, 4. Remove the original subsystem. Follow the instructions specified in Removing Avaya OA components on page 312. Changing subsystem attributes You might change names, IP addresses, and port numbers for subsystems on OA. This section includes the following topics: Example for changing a domain name on page 302 Changing the Historical subsystem system name or IP address on page 303 Installation and Configuration February

302 Chapter 5: Making changes to installed Avaya OA components Changing the naming service port number on page 308 Example for changing a domain name You might change the system name or IP address of the Historical subsystem server without physically moving the subsystem to another system. In this example, if the following subsystems are on the following servers: Historical subsystem on server A Real-time subsystem on server B Avaya IC subsystem on server A Report subsystem on server B To change the fully qualified domain name for the subsystems on server A perform the following: 1. For more information, see Avaya Operational Analyst Release 7.3.x Installation Planning and Prerequisites on the TCP/IP administration and DNS resolution prerequisites that are required on OA systems. 2. Change the fully qualified domain name for the Avaya IC subsystem. For more information, see Avaya Interaction Center 7.3.x documentation. 3. Change the fully-qualified domain name for the Historical subsystem. For more information, see Changing the Historical subsystem system name or IP address on page 303. To change the fully qualified domain name for the subsystems on server B perform the following: 1. For more information, see Avaya Operational Analyst Release 7.3.x Installation Planning and Prerequisites on the TCP/IP administration and DNS resolution prerequisites that are required on OA systems. 2. Change the fully qualified domain name for the Real-time subsystem: a. Enter the Subsystem screen in the OA Administration client. b. Highlight the Real-time subsystem that should be changed. c. Select Modify. d. Change the contents of the field labeled Internet domain name to the correct name. e. Select OK. f. Select Save in the Subsystem screen. 3. Change the fully qualified domain name for the Report subsystem: a. Enter the Subsystem screen in the OA Administration client. b. Highlight the Reports subsystem that should be changed. 302 Installation and Configuration February 2017

303 Changing subsystem attributes c. Select Modify. d. Change the contents of the field labeled Internet domain name to the correct name. e. Select OK. f. Select Save in the Subsystem screen. 4. Restart Tomcat on the Report subsystem (in this example, on Windows): a. Log in as an administrative user. b. Select Start > Programs > Administrative Tools > Services. c. Stop and Start the Tomcat service. For OA and earlier: Stop and Start the Stumbras-Tomcat service. For OA and later: Stop and Start the Avaya OA Reporting Application service. Changing the Historical subsystem system name or IP address You might change the system name or IP address of the Historical subsystem server without physically moving the subsystem to another system. These changes are only to the administration of the system. These steps assume that you have installed the database using the Administrator login that is local to the current system. If you use a different login during the installation, there might be issues with the database administration that you must resolve. You can resolve the issues according to the instructions of the database manufacturer. To change the name or IP address for the system where you have installed the Historical subsystem perform the following: 1. Log in using the appropriate user ID and password. For more information, see Avaya Operational Analyst Release 7.3.x Installation Planning and Prerequisites. 2. Stop all traffic to OA from every CMS and Avaya IC. For CMS: 1. Go to the Interface Services window and highlight each forwarder for each CMS. That is, the Subsystem column contains the name of the CMS. 2. Press View Status. 3. Highlight them again. 4. Select Disable and Save. For Avaya IC: 1. Go to the IC Manager for each Avaya IC. Installation and Configuration February

304 Chapter 5: Making changes to installed Avaya OA components 2. In the Server tab, highlight the Event Collector and stop it. 3. In the Server tab, highlight the Event Collector Bridge and stop it. 3. Follow the operating system instructions for changing a fully qualified domain name or IP address. On Windows, this includes using Control Panel to change the domain of the system. Make necessary changes to the DNS server IP addresses. Do not use the hosts file to resolve hostnames to IP addresses in OA configurations. Ensure that DNS administration resolves all system names in the same way. 4. On a Windows system, restart the system, and log in to the new domain. 5. On the Historical server, update the following files manually: The file path on Solaris and AIX is $PABASE/data/admin/. The file path on Windows is %PABASE%\data\admin\. Change the hostname and service properties in the db.properties file from: hostname=<old-machine-name> service =<old-machine-name>.<db-instance-name> to: hostname=<new-machine-name> service =<new-machine-name>.<db-instance-name> Change the REPORT_GROUP, ADMIN_GROUP and RWRITER_GROUP properties in the autserver.properties file (Windows) from: ADMIN_GROUP =[old-domain-name]\\<admin-client-user-group> REPORT_GROUP =[old-domain-name]\\<report-servr-user-group> RWRITER_GROUP =[old-domain-name]\\<report-writer-user-group> to: ADMIN_GROUP =[new-domain-name]\\<admin-client-user-group> REPORT_GROUP =[new-domain-name]\\<report-servr-user-group> RWRITER_GROUP =[new-domain-name]\\<report-writer-user-group> 304 Installation and Configuration February 2017

305 Changing subsystem attributes Change the REPORT_GROUP and ADMIN_GROUP properties in the autserver.properties file (Solaris and AIX) from: ADMIN_GROUP =[old-machine-name]\<admin-client-user-group> REPORT_GROUP =[old-machine-name]\<report-servr-user-group> RWRITER_GROUP =[old-machine-name]\\<report-writer-user-group> to: ADMIN_GROUP =[new-machine-name]\<admin-client-user-group> REPORT_GROUP =[new-machine-name]\<report-servr-user-group> RWRITER_GROUP =[new-machine-name]\\<report-writer-user-group> 6. Stop OA by doing one of the following: On Windows: 1. Select Start > Programs > Administrative Tools > Services. 2. Select Avaya Business Intelligence Service. 3. Select Action > Stop. On Solaris and AIX, enter the following commands:. /opt/bi/.profile pa stop all 7. Change the following properties in the server.properties file from: histserver=[name of historical server] reportsserver=[name of reports server] histdbserver=[name of database server] histdbname=[name of database server] to histserver=[new name of historical server] reportsserver=[new name of reports server] histdbserver=[new name of database server] histdbname=[new name of database server] If the name of the particular server is fully qualified, the new name must be fully qualified. If the name of the particular server is not fully qualified, the new name must not be fully qualified. If the name is blank, no change is necessary. 8. Stop and start Orbacus Naming Service. On Windows: Installation and Configuration February

306 Chapter 5: Making changes to installed Avaya OA components 1. Select Start > Programs > Administrative Tools > Services. 2. Select ORBacus Naming Service. 3. Select Action > Stop. 4. Select Action > Start. On Solaris and AIX: 1. Edit /etc/inittab and change the following lines from: in:234:respawn:/opt/bi/bin/initsrv.sh nm:234:respawn:/opt/bi/bin/nameserv.sh to: in:234:off:/opt/bi/bin/initsrv.sh nm:234:off:/opt/bi/bin/nameserv.sh 2. Enter: init q This turns these daemons off. To turn the daemons on, change the same lines back to respawn and enter the init q command again. 9. Stop and start the Web server. On Windows: 1. Select Start > Programs > Administrative Tools > Services. 2. Select Tomcat service. For OA and earlier: Select the Stumbras-Tomcat service. For OA and later: Select the Avaya OA Reporting Application service. 3. Select Action > Stop. 4. Select Action > Start. On Solaris or AIX, enter the following commands:. /opt/bi/.profile cd /opt/bi/stumbras/tomcat/bin For OA and earlier:./shutdown.sh./startup.sh For OA and later:./stopoareport.sh./startoareport.sh 306 Installation and Configuration February 2017

307 Changing subsystem attributes 10. Start OA: On Windows: 1. Select Start > Programs > Administrative Tools > Services. 2. Select Avaya Business Intelligence Service. 3. Click Action > Start. On Solaris and AIX: pa start all 11. On every server that is not a Historical server, manually update the following files: $PABASE/data/admin/server.properties (Solaris and AIX) %PABASE%\data\admin\server.properties (Windows) Change the histserver property from: histserver=<old-machine-name> to: histserver=<new-machine-name> 12. On every server that is not a Historical server, use the console to stop and start OA, entering: pa stop all pa start all! Important: Stopping and starting all OA processes forces to restart and reread the server.properties file. OA does not function correctly if you do not perform this step. 13. On every Windows client computer where you have installed the OA Administration client, edit the %PABASE%\AdminPol.html and %PABASE%\AdminSig.html files. You can change the server name to the server name where you have installed the new Historical subsystem. Change the SERVER_NAME property from: <PARAM NAME="SERVER_NAME" VALUE="OLD-NAME"> SERVER_NAME="OLD-NAME" to: <PARAM NAME="SERVER_NAME" VALUE="NEW-NAME"> SERVER_NAME="NEW-NAME" 14. Restart the client software. Important: Installation and Configuration February

308 Chapter 5: Making changes to installed Avaya OA components 15. Open the Subsystems window of the OA Administration client. An asterisk (*) next to the Historical subsystem indicates that the hostname and the IP address are no longer synchronized. Change the domain name to the new domain. Click OK and then Save. 16. Enable the forwarders for CMS. 17. Start the Event Collector and Event Collector Bridge for Avaya IC using IC Manager. Changing the naming service port number You might change the port number that the ORBacus naming service uses. This change is required if you are using another product that accesses the same port number as the default value used by OA. You can change the default port number, 10000, to anything that the operating system supports. The instructions below explain how to manually change the port number for the naming service and the OA software. You must apply the port number change to all hosts of the system. To change the naming service port number: 1. Log in using an OA user ID and password. For more information, see Avaya Operational Analyst Release 7.3.x Installation Planning and Prerequisites. 2. In a command prompt window, enter:. /opt/bi/.profile (Solaris and AIX) pa stop all (Windows, Solaris, and AIX) 3. On Windows only: a. Select Start > Programs > Administrative Tools > Services. b. Stop the following services: Avaya Business Intelligence service ORBacus Naming Service Tomcat service - For OA and earlier the service name is Stumbras-Tomcat. - For OA and later the service name is Avaya OA Reporting Application. 4. In the following file on the OA server running the Report subsystem: %PABASE%\stumbras\webapp\WEB-INF\config\ConfigService\ ConfigureService.xml (Windows) $PABASE/strumbas/tomcat/webapps/ROOT/WEB-INF/config/ RTPAService/RTPAService.properties (Solaris or AIX) change on the line <Port>10000</Port> to the port number you want to use: 308 Installation and Configuration February 2017

309 Changing subsystem attributes 5. In the following file on all OA servers, the Avaya IC server where you have installed the EC, and to the computers running the Administration Client: %PABASE%\data\admin\server.properties (Windows) $PABASE/data/admin/server.properties (Solaris and AIX) add the line NSPort=<port> where <port> is the same port number you used in the ConfigureService.xml file in the previous step. 6. In the registry editor (regedit) on a Windows server, change the port value Dooc.naming.port=10000 located at HKEY_LOCAL_MACHINE\SYSTEM\ CurrentControlSet\Services\NamingService\Parameters and restart the service. Do this on all Windows OA servers, the Windows Avaya IC server where you have installed the EC, and to the Windows computers running the Administration Client. 7. Using sqlplus for Oracle, Query Analyzer for Microsoft SQL, and db2 for DB2, apply the following query to the Historical database, once for each Real-time host: update dcproperty set value = 'corbaname::hostname:port#crm_bi.root/real.pkg/ RTDSSDSGatewayV1.obj' where: value is similar to N'%<hostname>%RTDSSDSGatewayV1.obj' name is similar to 'RTPAConfig.Server%CorbaURL'; hostname is the name of one of the real time subsystem host. port is the same port number you used for the OA hosts. You must run this query for each Real-time host. For example, if you have two Real-time hosts, called firstrt and otherrt, and you want to change the port number to 5000, you must run these two queries: update dcproperty set value = 'corbaname::firstrt:5000#crm_bi.root/real.pkg/ RTDSSDSGatewayV1.obj' update dcproperty set value = 'corbaname::otherrt:5000#crm_bi.root/real.pkg/ RTDSSDSGatewayV1.obj' update dcproperty set value = 120 where service_name = stumbras and name = RTPAConfig.Server.1.CorbaURL 8. On Windows only: a. Select Start > Programs > Administrative Tools > Services. Installation and Configuration February

310 Chapter 5: Making changes to installed Avaya OA components CAUTION: b. Start the following services: Avaya Business Intelligence service ORBacus Naming Service Tomcat service. - For OA and earlier the service name is Stumbras-Tomcat. - For OA and later the service name is Avaya OA Reporting Application. 9. On Solaris, Linux, and AIX: a. In the file $PABASE/bin/nameserv.sh, update the line -Dooc.naming.port=10000 where is the port number you want to use. b. Make a backup copy of the /etc/inittab file. Use the command: cp /etc/inittab /etc/inittab.orig! CAUTION: Be careful when editing the /etc/inittab file. Errors can cause the system to stop working. c. Open /etc/inittab and change the following lines from: in:234:respawn:/opt/bi/bin/initsrv.sh nm:234:respawn:/opt/bi/bin/nameserv.sh to: in:234:off:/opt/bi/bin/initsrv.sh nm:234:off:/opt/bi/bin/nameserv.sh d. Enter: init q This turns these daemons off. To turn the daemons on, change the same lines back to respawn and enter the init q command again. 10. In a command prompt window, enter: pa start all To change the naming service port number on a Windows platform where the EC Server is installed: 1. Access the IC Manager tool. 2. Select the Configuration tab. 3. Add a new name/value pair for NSPort=port where port is the same port number you used for the OA hosts. You do this by clicking on the ->= (New) icon in the configuration tab dialog box. 310 Installation and Configuration February 2017

311 Changing subsystem attributes To change the naming service port number on a Solaris SPARC platform running CMS: CAUTION: 1. Log in as root. 2. In a terminal window, enter:. /opt/bi/.profile pa stop all 3. In the file $PABASE/data/admin/server.properties, add the line NSPort=port where port is the port number you want to use. 4. In the file $PABASE/bin/nameserv.sh, update the line -Oaport port where port is the port number you want to use. 5. Make a backup copy of the /etc/inittab file. Use the command: cp /etc/inittab /etc/inittab.orig! CAUTION: Be careful when editing the /etc/inittab file. Errors can cause the system to stop working. 6. Open /etc/inittab and change the following lines from: in:234:respawn:/opt/bi/bin/initsrv.sh nm:234:respawn:/opt/bi/bin/nameserv.sh to: in:234:off:/opt/bi/bin/initsrv.sh nm:234:off:/opt/bi/bin/nameserv.sh 7. Enter: init q This turns these daemons off. To turn the daemons on, change the same lines back to respawn and enter the init q command again. 8. Enter: pa start all To change the naming service port number on RHEL platform running CMS: 1. Log in as root. 2. In a terminal window, enter:. /opt/bi/.profile pa stop all Installation and Configuration February

312 Chapter 5: Making changes to installed Avaya OA components 3. In the file $PABASE/data/admin/server.properties, add the line NSPort=port where port is the port number you want to use. 4. In the file $PABASE/bin/nameserv.sh, update the line -IIOPport port where port is the port number you want to use. 5. Run the following commands: initctl stop initsrv initctl stop nameserv These commands turns the daemons off. 6. To turn the daemons on, run the following commands: initctl start initsrv initctl start nameserv 7. Run the following command to start OA: pa start all Removing Avaya OA components You can remove each components or all OA software. When you delete a source subsystem, you do not remove the subsystem from the database. The system does not remove the associated from the database, which lets reports to continue to access the data collected from a source before the deletion.! CAUTION: CAUTION: Before removing any components, Avaya recommends that you do a backup of the database and the file systems. This section includes the following topics: Considerations when removing OA components on page 313 Removing Avaya OA components from Windows system on page 313 Removing Avaya OA software from Solaris SPARC system on page 319 Removing Avaya OA software from Red Hat Enterprise Linux (RHEL) system on page 328 Removing Avaya OA software from the AIX system on page Installation and Configuration February 2017

313 Removing Avaya OA components Considerations when removing OA components When removing OA components, decide the following: If you remove the Real-time subsystem from a server, the supporting TimesTen software is not removed. If you have no need to keep the software on that server, you can manually remove the TimesTen software. Removing Avaya OA components from Windows system To remove OA components on Windows: 1. Open Administration Client and remove the subsystems you want to remove from the system. 2. Stop all OA processes. For more information, see Stopping or starting processes and services before making changes on page Log in as a user with administration privileges. 4. If you want to remove the Reporting subsystem, stop Stumbras. 5. If Terminal Services is enabled, enter change user /install in a command prompt window. 6. From the Windows Start menu, click Control Panel > Programs > Programs and Features. The system displays the Programs and Features dialog box. 7. Double-click Add or Remove Programs. The system displays the Add or Remove Programs dialog box. 8. Under Avaya Operational Analyst, select Change/Remove. After several seconds, the Initializing wizard window displays, followed by the Welcome dialog box. If errors appear on this dialog box, the removal process has failed and you must remove the software manually. Contact support for help. Important:! Important: You can stop the removal anytime by clicking Cancel before you run the actual removal of files (see Step 12). If you click Cancel, you are asked to confirm your intention to cancel. If you cancel, the system stops the removal and restores the system is to the previous state. Installation and Configuration February

314 Chapter 5: Making changes to installed Avaya OA components 9. Click Next. The Feature Selection dialog box displays. Installed Components are shown with check marks. Components not installed are dimmed or hidden. CAUTION:! CAUTION: Any component that is selected are removed. If you want to remove only some components, ensure that the components you want to keep are not selected. Do not select or clear the main Product Uninstallation or Install Supporting Applications check boxes. The software automatically sets these options depending on what components you are removing. 10. Leave checks in the components you want to remove, and clear the check marks for the components you want to keep. 314 Installation and Configuration February 2017

315 Removing Avaya OA components Important:! Important: After selecting or clearing a check box, there might be a delay before the dialog box refreshes and you see the check mark or the check mark is cleared. This delay might take a few seconds. Do not select or clear another check box until the dialog box refreshes and you can see that the check box is select or clear. The following example shows that you are removing the Reporting subsystem and the Data API Utility. 11. Click Next. A confirmation dialog box displays. Installation and Configuration February

316 Chapter 5: Making changes to installed Avaya OA components CAUTION: CAUTION:! CAUTION: Do not close the dialog box after you have clicked Next in the following step. If you close the dialog box after the removal has started, you disrupt the removal. You must contact Avaya support to do a manual cleanup of the removal. 12. Click Next. The removal process begins. If you receive any messages, note the messages and click Next to continue. When the removal, which takes several minutes, is complete, the system displays the Uninstall Complete dialog box.! CAUTION: If you get any failure messages saying that the removal cannot complete, do not try to do another removal. Escalate the problem through normal channels. 13. When the removal process completes, which takes several minutes, the removal complete dialog box displays. 14. Click Next. The Restart System dialog box displays. 15. Select the option to restart your system now and click Next.! Important: You must always restart a Windows server for OA to operate properly. If the system does not request you to restart the server, you must manually restart the server. 16. Perform one of the following: If you removed all components from this server, you are complete. If you did not remove all components from this server, continue with Step Log in using an OA user ID and password. For more information, see Avaya Operational Analyst Release 7.3.x Installation Planning and Prerequisites. 18. Open a command prompt window. Important: 316 Installation and Configuration February 2017

317 Removing Avaya OA components 19. In the command prompt window, enter the following command to determine what processes are running: pa list The system displays a message similar to the following:. system boot Dec 20 07:54. run-level 4 Dec 31 10:23 4 java. Dec 20 07: id=admb java. Dec 20 07: id=adm0 java. Jan 02 16: id=ams java. Dec 20 07: id=aut java. Dec 20 07: id=schd... There can be several Java entries, and these lines cannot have an exit code at the end of the line. If the system displays any exit codes on the Java entries, that process is not running. Escalate the problem to Avaya Technical Support. The id=aut and id=schd only displays when you have installed the Historical subsystem. The recorder entries display only if you are collecting data from CMS or Avaya IC. Forwarder entries might display on a server that you have installed the Real-time subsystem. 20. If you get the message mom is not active, enter: pa start all 21. Repeat Step 4 to verify that OA has started. Installation and Configuration February

318 Chapter 5: Making changes to installed Avaya OA components 22. Enter: oalist The system displays a message similar to the following: Subsystems installed Historical Real Time Reports Data API Utility Source-EC Advanced Reports Administration Client Server Names Historical: punoasvorsr03 Historical Database: <IP_Address_of_Historical_Database_System> Database information Type: MSSQL AdminID: sa UserID: oadba Instance Name: MSSQLSERVER Port Number: 1433 OA DB Name: oadb IC UserID: repository IC Repository DB Name: repository Using a Backend/Remote Database IC Historical Tables created User information OA User ID: biadmin Domain: punoadom Group ID: oaadmin Active Directory Server or Localhost Information ADS Version: 3 ADS Port: 389 ADS Admin Group: CN=oaadmin,OU=OA Admins,DC=punoadom,DC=avaya,DC=com ADS Report Group: CN=oarpt,OU=OA Admins,DC=punoadom,DC=avaya,DC=com ADS Report Writer Group: CN=oawriter,OU=OA Admins,DC=punoadom,DC=avaya,DC=com Admin Client Locale Admin Client Locale: en_us OA Software information Version Installed: Select Start > Programs > Administrative Tools > Services. 318 Installation and Configuration February 2017

319 Removing Avaya OA components 24. Validate that the following services are running and are set to run automatically. If they are not administered to start automatically, administer them as such. If you have installed the Historical subsystem, check for the following: - Avaya Business Intelligence Service - ORBacus Naming Service If you have installed the Real-time subsystem, check for the following: - Avaya Business Intelligence Service - ORBacus Naming Service - TimesTen Data Manager If you have installed the Report subsystem, check for the following: - Avaya Business Intelligence service - ORBacus Naming Service - Tomcat service. - For OA and earlier the service name is Stumbras-Tomcat. - For OA and later the service name is Avaya OA Reporting Application. If you have installed the Source-EC subsystem, check for the following: - ORBacus Naming Service 25. If you are not successful in starting OA, see Avaya Operational Analyst Release 7.3.x Maintenance and Troubleshooting Guide for more troubleshooting information. Removing Avaya OA software from Solaris SPARC system To remove OA software on Solaris perform the following: 1. Open Administration Client and remove the subsystems you want to remove from the system. 2. Stop all OA processes. For more information, see Stopping or starting processes and services before making changes on page Log in as root. 4. If you want to remove the Reporting subsystem, stop Stumbras. 5. Move to the home folder of the OA User ID used when OA was installed. For example, if you used the biadmin user ID when OA was installed and you originally installed OA in the default location, enter the following commands:. /opt/bi/.profile cd /export/home/biadmin Installation and Configuration February

320 Chapter 5: Making changes to installed Avaya OA components 6. Enter: ls _uninst* This lists the files in the uninstall folder. There might be more than one uninstall folder. The system displays a message similar to the following: _uninst _uninst2 _uninst3 7. Enter: cd _uninstx where X is the highest numbered uninstall folder, if there is more than one folder. 8. Enter one of the following commands, depending on which one you find in the folder:./oaremove.bin or./aoaremove.bin After several seconds, the Initializing wizard window displays, followed by the Welcome dialog box. If errors appear on this dialog box, the removal process has failed and you must remove the software manually. Contact support for help. Important:! Important: You can stop the removal anytime by clicking Cancel before you run the actual removal of files (see Step 12). If you click Cancel, you are asked to confirm your intention to cancel. If you cancel, the system stops the removal and restores the system to the previous state. 320 Installation and Configuration February 2017

321 Removing Avaya OA components 9. Click Next. The Feature Selection dialog box displays. Components installed have check marks. Components not installed are dimmed or hidden. CAUTION:! CAUTION: Any component selected is removed. If you want to remove only some components, ensure that the components you want to keep are not selected. Do not select or clear the main Product Uninstallation or Install Supporting Applications check boxes. The software automatically sets these options depending on what components you are removing. 10. Leave checks in the components you want to remove, and clear the check marks for the components you want to keep. Installation and Configuration February

322 Chapter 5: Making changes to installed Avaya OA components Important:! Important: After selecting or clearing a check box, there might be a delay before the dialog box refreshes and you see the check mark or the check mark is cleared. This delay might take a few seconds. Do not select or clear another check box until the dialog box refreshes and you can see that the check box is select or clear. The following example shows that you are removing the Historical subsystem and the Real Time subsystem. 11. Click Next. A confirmation dialog box displays. 322 Installation and Configuration February 2017

323 Removing Avaya OA components CAUTION: CAUTION: CAUTION:! CAUTION: Do not close the dialog box after you have clicked Next in the following step. If you close the dialog box after the removal has started, you disrupt the removal. You must contact Avaya support to do a manual cleanup of the removal. 12. Click Next. The removal process begins. If you receive any messages, note the messages and click Next to continue. When the removal is complete, which takes several minutes, the Uninstall Complete dialog box displays.! CAUTION: If you get any failure messages saying that the removal is not complete, do not try to do another removal. Escalate the problem through normal channels. 13. Click Next. The removal is complete. 14. Perform one of the following: Remove Avaya OA from the package list using the following commands as a root user: cd /var/sadm/pkg rm AOA/install/preremove pkgrm AOA If you did not remove all components from this server, continue with Step Log out of the desktop environment. 16. Log in using an OA user ID and password. For more information, see Avaya Operational Analyst Release 7.3.x Installation Planning and Prerequisites.! CAUTION: Do not use any OA commands while logged in as root. Using the root login ID on these commands changes ownership of files and makes them unusable by the OA user ID. 17. Enter:. /opt/bi/.profile Installation and Configuration February

324 Chapter 5: Making changes to installed Avaya OA components 18. Enter the following command to determine what processes are running: pa list The system displays a message similar to the following:. system boot Dec 20 07:54. run-level 4 Dec 31 10:23 4 java. Dec 20 07: id=admb java. Dec 20 07: id=adm0 java. Jan 02 16: id=ams java. Dec 20 07: id=aut java. Dec 20 07: id=schd... There can be several Java entries, and these lines cannot have an exit code at the end of the line. If the system displays any exit codes on the Java entries, that process is not running. Escalate the problem to Avaya Technical Support. The id=aut and id=schd only displays when you have installed the Historical subsystem. The recorder entries display only if you are collecting data from CMS or Avaya IC. Forwarder entries might display on a server that you have installed the Real-time subsystem. 19. If you get the message mom is not active, enter: pa start all 20. Repeat Step 4 to verify that OA has started. 21. If you are not successful starting OA, see Avaya Operational Analyst Release 7.3.x Maintenance and Troubleshooting Guide for more troubleshooting information. 324 Installation and Configuration February 2017

325 Removing Avaya OA components 22. Enter: oalist The system displays a message similar to the following: Subsystems installed Historical Real Time Reports Data API Utility Source-EC Server Names Historical: puoadvsolsr14 Historical Database: <IP_Address_of_Historical_Database_System> Reports: puoadvsolsr14 Database information Type: ORACLE AdminID: sys UserID: oadba Instance Name: oa7211g Port Number: 1521 IC UserID: repository Using a Backend/Remote Database IC Historical Tables created User information OA User ID: biadmin Group ID: oaadmin Reports information Reports Group ID: oarpt Report Writer Group ID: oawriter Tomcat Home: /export/home/biadmin/bi/stumbras/tomcat Tomcat Port: 9080 OA Software information Version Installed: If you have installed the Historical subsystem, use the following commands and responses to verify that the required services are running. If the services are not running, escalate the problem using the normal channels. a. Enter the following command to determine if the Avaya Business Intelligence Service is running: ps -ef grep initsrv The system displays a message similar to the following: root Dec 27? 0:06 /opt/bi/bin/initsrv -n oaadmin -v 30 biadmin :28:00 pts/11 0:00 grep initsrv Installation and Configuration February

326 Chapter 5: Making changes to installed Avaya OA components b. Enter the following command to determine if the ORBacus Naming Service is running: ps -ef grep naming The system displays a message similar to the following: biadmin Oct 21? 6:48 /export/home/biadmin/ jre<version_number>/bin/java -Dooc.naming.port=10000 com.ooc.cosn biadmin :27:35 pts/3 0:00 grep naming 24. If you have installed the Real-time subsystem, use the following commands and responses to verify that the required services are running. If the services are not running, escalate the problem using the normal channels. a. Enter the following command to determine if the Avaya Business Intelligence Service is running: ps -ef grep initsrv The system displays a message similar to the following: root Dec 27? 0:06 /opt/bi/bin/initsrv -n oaadmin -v 30 biadmin :28:00 pts/11 0:00 grep initsrv b. Enter the following command to determine if the ORBacus Naming Service is running: ps -ef grep naming The system displays a message similar to the following: biadmin Oct 21? 6:48 /export/home/biadmin/ jre<version_number>/bin/java -Dooc.naming.port=10000 com.ooc.cosn biadmin :27:35 pts/3 0:00 grep naming c. Enter the following command to determine if the TimesTen Data Manager is running: ps -ef grep timesten The system displays a message similar to the following: root Dec 23? 0:01 /export/home/biadmin/timesten5.1.34/ TimesTen/avaya_bi/bin/timestend root Dec 23? 0:00 /export/home/biadmin/timesten5.1.34/ TimesTen/avaya_bi/bin/timestensubd -id 0 root Dec 23? 0:00 /export/home/biadmin/timesten5.1.34/ TimesTen/avaya_bi/bin/timestensubd -id 1 root Dec 23? 0:00 /export/home/biadmin/timesten5.1.34/ TimesTen/avaya_bi/bin/timestensubd -id 2 root Dec 23? 0:00 /export/home/biadmin/timesten5.1.34/ TimesTen/avaya_bi/bin/timestensubd -id 3 biadmin :34:22 pts/11 0:00 grep timesten 326 Installation and Configuration February 2017

327 Removing Avaya OA components 25. If you have installed the Report subsystem, use the following commands and responses to verify that the required services are running. If the services are not running, escalate the problem using the normal channels. a. Enter the following command to determine if the Avaya Business Intelligence Service is running: ps -ef grep initsrv The system displays a message similar to the following: root Jan 20? 0:06 /opt/bi/bin/initsrv -n oaadmin -v 30 biadmin :28:00 pts/11 0:00 grep initsrv b. Enter the following command to determine if the ORBacus Naming Service is running: ps -ef grep naming The system displays a message similar to the following: biadmin Jan 20? 6:48 /export/home/biadmin/ jre<version_number>/bin/java -Dooc.naming.port=10000 com.ooc.cosn biadmin :27:35 pts/3 0:00 grep naming 26. If you have installed the Source-EC subsystem, use the following commands and responses to verify that the required services are running. If the services are not running, escalate the problem using the normal channels. a. Enter the following command to determine if the ORBacus Naming Service is running: ps -ef grep naming The system displays a message similar to the following: biadmin Jan 20? 6:48 /export/home/biadmin/ jre<version_number>/bin/java -Dooc.naming.port=10000 com.ooc.cosn biadmin :27:35 pts/3 0:00 grep naming 27. Start the Tomcat server after you configure the Admin client. For more information, see Administration client options on page 168. a. Log in to the Solaris system using an Avaya OA user ID and password. For more information, see Avaya Operational Analyst Release 7.3.x Installation Planning and Prerequisites. CAUTION:! CAUTION: Do not use any Avaya OA commands while logged in as root. Using the root login ID on these commands changes ownership of files and makes them unusable by the Avaya OA user ID. b. Enter the command:./opt/bi/.profile. Installation and Configuration February

328 Chapter 5: Making changes to installed Avaya OA components c. Go to the Tomcat server location. Enter the command: cd /opt/bi/stumbras/tomcat/bin. d. Start the Tomcat server. Enter the command: For OA and earlier:./startup.sh For OA and later:./startoareport.sh 28. Check the Tomcat server logs to verify that Tomcat is running successfully. a. Go to the $PABASE/stumbras/tomcat/logs/ folder. b. Enter the command: vi catalina.out 29. Check if the Tomcat server is running successfully. a. Go to the $PABASE/stumbras/tomcat/conf folder. b. Check if the PID.txt file is present in the folder. The PID.txt file indicates that the process ID of the Tomcat server is registered in the PID.txt file. 30. Stop the Tomcat server. a. Enter the command:./opt/bi/.profile. b. Go to the Tomcat server location. Enter the command: cd /opt/bi/stumbras/tomcat/bin. c. Stop the Tomcat server. Enter the command: For OA and earlier:./shutdown.sh -force For OA and later:./stopoareport.sh -force Removing Avaya OA software from Red Hat Enterprise Linux (RHEL) system To remove OA software from the RHEL system perform the following: 1. Open Administration Client and remove the subsystems you want to remove from the system. 328 Installation and Configuration February 2017

329 Removing Avaya OA components 2. Stop all OA processes. For more information, see Stopping or starting processes and services before making changes on page Log in as root. 4. Move to the home folder of the OA User ID used when OA was installed. For example, if you used the biadmin user ID when OA was installed and you originally installed OA in the default location, enter the following commands:. /opt/bi/.profile cd /export/home/biadmin 5. Enter: ls _uninst* This lists the files in the uninstall folder. There might be more than one uninstall folder. The system displays a message similar to the following: _uninst _uninst2 _uninst3 6. Enter: cd _uninstx where X is the highest numbered uninstall folder, if there is more than one folder. 7. Enter one of the following commands, depending on which one you find in the folder:./oaremove.bin or./aoaremove.bin After several seconds, the Initializing wizard window displays, followed by the Welcome dialog box. If errors appear on this dialog box, the removal process has failed and you must remove the software manually. Contact support for help. Important:! Important: You can stop the removal anytime by clicking Cancel before you run the actual removal of files (see Step 12). If you click Cancel, you are asked to confirm your intention to cancel. If you cancel, the system stops the removal and restores the system to the previous state. Installation and Configuration February

330 Chapter 5: Making changes to installed Avaya OA components 8. Click Next. The Feature Selection dialog box displays. Components installed are shown with the corresponding check box selected. Components not installed are dimmed or hidden. CAUTION:! CAUTION: Any component that you select is removed. If you want to remove only some components, ensure that the components you want to keep are not selected. Do not select or clear the main Product Uninstallation or Install Supporting Applications check boxes. The software automatically sets these options depending on what components you are removing. 9. Leave checks in the components you want to remove, and clear the check marks for the components you want to keep. Important:! Important: After selecting or clearing a check box, there might be a delay before the dialog box refreshes and you see the check mark or the check mark is cleared. This delay might take a few seconds. Do not select or clear another check box until the dialog box refreshes and you can see that the check box is select or clear. 330 Installation and Configuration February 2017

331 Removing Avaya OA components 10. Click Next. A confirmation dialog box displays. CAUTION: CAUTION:! CAUTION: Do not close the dialog box after you have clicked Next in the following step. If you close the dialog box after the removal has started, you disrupt the removal. You must contact Avaya support to do a manual cleanup of the removal. 11. Click Next. The install process begins. If you receive any messages, note the messages and click Next to continue. When the removal is complete, which takes several minutes, the Uninstall Complete dialog box displays.! CAUTION: If you get any failure messages saying that the removal is not complete, do not try to do another removal. Escalate the problem through normal channels. 12. Click Next. The removal is complete. 13. If you did not remove all components from this server, continue with Step Log out of the desktop environment. 15. Log in using an OA user ID and password. For more information, see Avaya Operational Analyst Release 7.3.x Installation Planning and Prerequisites. Installation and Configuration February

332 Chapter 5: Making changes to installed Avaya OA components CAUTION:! CAUTION: Do not use any OA commands while logged in as root. Using the root login ID on these commands changes ownership of files and makes them unusable by the OA user ID. 16. Enter:. /opt/bi/.profile 17. Enter the following command to determine what processes are running: pa list The system displays a message similar to the following: (cmsjune74)-(root)=# pa list all. system boot Oct 1 17:13. run-level 4 Oct 1 17:13 4 java. Oct 1 17:13 old id=admb java. Oct 1 17:13 old id=adm0 java. Oct 1 17:13 old id=ams There can be several Java entries, and these lines cannot have an exit code at the end of the line. If the system displays any exit codes on the Java entries, that process is not running. Escalate the problem to Avaya Technical Support. The id=aut and id=schd only displays when you have installed the Historical subsystem. The recorder entries display only if you are collecting data from CMS or Avaya IC. Forwarder entries might display on a server that you have installed the Real-time subsystem. 18. If you get the message mom is not active, enter: pa start all 19. Repeat Step 4 to verify that OA has started. 20. If you are not successful starting OA, see Avaya Operational Analyst Release 7.3.x Maintenance and Troubleshooting Guide for more troubleshooting information. 332 Installation and Configuration February 2017

333 Removing Avaya OA components 21. Enter: oalist The system displays a message similar to the following: Subsystems installed Data API Utility Source-CMS Server Names Historical: icdev84 Database information Type: UNSET User information CMS ID: informix OA User ID: biadmin Group ID: oaadmin OA Software information Version Installed: Enter the following command to determine if the Avaya Business Intelligence Service is running: ps -ef grep initsrv The system displays a message similar to the following: root :12? 00:00:00 /opt/bi/bin/initsrv -n oaadmin -v Enter the following command to determine if the ORBacus Naming Service is running: ps -ef grep CosNaming The system displays a message similar to the following: root :12? 00:00:00 /export/home/biadmin/ jre<version_number>/bin/java com.ooc.cosnaming.server -IIOPport Removing Avaya OA software from the AIX system To remove OA software from the AIX system: CAUTION:! CAUTION: Stop Tomcat before removing the Report subsystem. 1. Open Administration Client and remove the subsystems you want to remove from the system. Installation and Configuration February

334 Chapter 5: Making changes to installed Avaya OA components 2. Stop all OA processes. For more information, see Stopping or starting processes and services before making changes on page Log in as root. 4. To remove the Reporting subsystem, stop Stumbras. 5. To set the monitor display, enter: export DISPLAY=hostname:0.0 where hostname is the name of the server. 6. Move to the home folder of the OA User ID used when OA was installed. For example, if you used the biadmin user ID when OA was installed and you originally installed OA in the default location, enter the following commands:. /opt/bi/.profile cd /home/biadmin/_uninst 7. Enter:./OARemove.bin After several seconds, the Initializing wizard window displays, followed by the Welcome dialog box. If errors appear on this dialog box, the removal process has failed and you must remove the software manually. Contact support for help. Important:! Important: You can stop the removal anytime by clicking Cancel before you run the actual removal of files (see Step 10). If you click Cancel, you are asked to confirm your intention to cancel. If you cancel, the system stops the removal and restores the system to the previous state. 334 Installation and Configuration February 2017

335 Removing Avaya OA components 8. Click Next. The Feature Selection dialog box displays. Components installed are shown with check marks. Components not installed are dimmed or hidden. CAUTION:! CAUTION: Any component you select is removed. If you want to remove only some components, ensure that the components you want to keep are not selected. Do not select or clear the main Product Uninstallation or Install Supporting Applications check boxes. The software automatically sets these options depending on what components you are removing. 9. Leave checks in the components you want to remove, and clear the check marks for the components you want to keep. Important:! Important: After selecting or clearing a check box, there might be a delay before the dialog box refreshes and you see the check mark or the check mark is cleared. This delay might take a few seconds. Do not select or clear another check box until the dialog box refreshes and you can see that the check box is select or clear. Installation and Configuration February

336 Chapter 5: Making changes to installed Avaya OA components 10. Click Next. A confirmation dialog box displays. CAUTION: CAUTION:! CAUTION: Do not close the dialog box after you have clicked Next in the following step. If you close the dialog box after the removal has started, you disrupt the removal. You must contact Avaya support to do a manual cleanup of the removal. 11. Click Next. The removal process begins. If you receive any messages, note the messages and click Next to continue. When the removal is complete, which takes several minutes, the Uninstall Complete dialog box displays.! CAUTION: If you get any failure messages saying that the removal is not complete, do not try to do another removal. Escalate the problem through normal channels. 12. Click Next. The removal is complete. 13. Perform one of the following: If you removed all components from this server, you are complete. If you did not remove all components from this server, continue with Step Log out of the desktop environment. 15. Log in using an OA user ID and password (see Avaya Operational Analyst Release 7.3.x Installation Planning and Prerequisites). 336 Installation and Configuration February 2017

337 Removing Avaya OA components CAUTION:! CAUTION: Do not use any OA commands while logged in as root. Using the root login ID on these commands changes ownership of files and makes them unusable by the OA user ID. 16. Enter:. /opt/bi/.profile 17. Enter the following command to determine what processes are running: pa list The system displays a message similar to the following:. system boot Dec 20 07:54. run-level 4 Dec 31 10:23 4 java. Dec 20 07: id=admb java. Dec 20 07: id=adm0 java. Jan 02 16: id=ams java. Dec 20 07: id=aut java. Dec 20 07: id=schd There can be several Java entries, and these lines cannot have an exit code at the end of the line. If the system displays any exit codes on the Java entries, that process is not running. Escalate the problem to Avaya Technical Support. The id=aut and id=schd only displays when you have installed the Historical subsystem. The recorder entries display only if you are collecting data from CMS or Avaya IC. Forwarder entries might display on a server that you have installed the Real-time subsystem. 18. If OA is not running (mom is not active), enter: pa start all 19. Repeat Step 4 to verify that OA has started. 20. If you are not successful starting OA, see Avaya Operational Analyst Release 7.3.x Maintenance and Troubleshooting Guide for more troubleshooting information. Installation and Configuration February

338 Chapter 5: Making changes to installed Avaya OA components 21. Enter: oalist The system displays a message similar to the following: Subsystems installed Historical Real Time Reports Data API Utility Source-EC Server Names Historical: puoaaix7205 Historical Database: <IP_Address_of_Historical_Database_System> Database information Type: DB2 AdminID: db2inst1 UserID: db2inst1 Instance Name: db2inst1 Port Number: OA DB Name: girish OA DB Schema Name: oaschema IC UserID: repository IC Repository DB Name: repository Using a Backend/Remote Database IC Historical Tables created DB2 Path: /home/db2inst1 DB2 Library Path: /home/db2inst1/sqllib DB2 Version: 9.5.x User information OA User ID: biadmin Group ID: oaadmin Reports information Reports Group ID: oarpt Report Writer Group ID: oawriter Tomcat Home: /home/biadmin/bi/stumbras/tomcat Tomcat Port: 9080 OA Software information Version Installed: If you have installed the Historical subsystem, use the following commands and responses to verify that the required services are running. If the services are not running, escalate the problem using the normal channels. 338 Installation and Configuration February 2017

339 Removing Avaya OA components a. Enter the following command to determine if the Avaya Business Intelligence Service is running: ps -ef grep initsrv The system displays a message similar to the following: root Dec 27? 0:06 /opt/bi/bin/initsrv -n oaadmin -v 30 biadmin :28:00 pts/11 0:00 grep initsrv b. Enter the following command to determine if the ORBacus Naming Service is running: ps -ef grep naming The system displays a message similar to the following: biadmin Oct 21? 6:48 /export/home/biadmin/ jre<version_number>/bin/java -Dooc.naming.port=10000 com.ooc.cosn biadmin :27:35 pts/3 0:00 grep naming 23. If you have installed the Real-time subsystem, use the following commands and responses to verify that the required services are running. If the services are not running, escalate the problem using the normal channels. a. Enter the following command to determine if the Avaya Business Intelligence Service is running: ps -ef grep initsrv The system displays a message similar to the following: root Dec 27? 0:06 /opt/bi/bin/initsrv -n oaadmin -v 30 biadmin :28:00 pts/11 0:00 grep initsrv b. Enter the following command to determine if the ORBacus Naming Service is running: ps -ef grep naming The system displays a message similar to the following: biadmin Oct 21? 6:48 /export/home/biadmin/ jre<version_number>/bin/java -Dooc.naming.port=10000 com.ooc.cosn biadmin :27:35 pts/3 0:00 grep naming Installation and Configuration February

340 Chapter 5: Making changes to installed Avaya OA components c. Enter the following command to determine if the TimesTen Data Manager is running: ps -ef grep timesten The system displays a message similar to the following: biadmin :01:34 pts/0 0:00 grep timesten root Apr 16-0:17 /home/biadmin/timesten5.1.34/ TimesTen/avaya_bi/bin/timestensubd -verbose -id 2 -facility user root Apr 16-0:17 /home/biadmin/timesten5.1.34/ TimesTen/avaya_bi/bin/timestensubd -verbose -id 1 -facility user root Apr 16-3:35 /home/biadmin/timesten5.1.34/ TimesTen/avaya_bi/bin/timestensubd -verbose -id 3 -facility user root Apr 16-0:42 /home/biadmin/timesten5.1.34/ TimesTen/avaya_bi/bin/timestend -fg root Apr 16-0:18 /home/biadmin/timesten5.1.34/ TimesTen/avaya_bi/bin/timestensubd -verbose -id 0 -facility user 24. If you have installed the Source-EC subsystem, use the following commands and responses to verify that the required services are running. If the services are not running, escalate the problem using the normal channels. a. Enter the following command to determine if the ORBacus Naming Service is running: ps -ef grep naming The system displays a message similar to the following: biadmin Oct 21? 6:48 /export/home/biadmin/ jre<version_number>/bin/java -Dooc.naming.port=10000 com.ooc.cosn biadmin :27:35 pts/3 0:00 grep naming 25. If you have installed the Report subsystem, enter the following commands to stop and restart the Tomcat software:. /opt/bi/.profile cd /opt/bi/stumbras/tomcat/bin For OA and earlier:./shutdown.sh./startup.sh For OA and later:./stopoareport.sh./startoareport.sh 26. If you have installed the Report subsystem, use the following commands and responses to verify that the required services are running. If the services are not running, escalate the problem using the normal channels. 340 Installation and Configuration February 2017

341 Removing Avaya OA components a. Enter the following command to determine if the Avaya Business Intelligence Service is running: ps -ef grep initsrv The system displays a message similar to the following: root Dec 27? 0:06 /opt/bi/bin/initsrv -n oaadmin -v 30 biadmin :28:00 pts/11 0:00 grep initsrv b. Enter the following command to determine if the ORBacus Naming Service is running: ps -ef grep naming The system displays a message similar to the following: biadmin Oct 21? 6:48 /export/home/biadmin/ jre<version_number>/bin/java -Dooc.naming.port=10000 com.ooc.cosn biadmin :27:35 pts/3 0:00 grep naming c. Enter the following command to determine if Tomcat is running: ps -eaf grep catalina grep /opt/bi/stumbras/tomcat The system displays a message similar to the following: biadmin :27:59 pts/1 1:01 /home/biadmin/jre<version_number>/ bin/java -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager -Djava.util.l ogging.config.file=/opt/bi/stumbras/tomcat/conf/logging.properties -Djava.endors ed.dirs=/opt/bi/stumbras/tomcat/endorsed -classpath :/opt/bi/stumbras/tomcat/bin /bootstrap.jar -Dcatalina.base=/opt/BI/stumbras/tomcat -Dcatalina.home=/opt/BI/s tumbras/tomcat -Djava.io.tmpdir=/opt/BI/stumbras/tomcat/temp org.apache.catalina.startup.bootstrap start 27. To verify that OA reports are running using the Tomcat Administrative Console: a. In a browser window, enter: where report_server_fqdn is the fully qualified domain name of the server where you installed the Report subsystem. The port_number is the port number the system assigns to the Tomcat Administrative Console. For example, b. In the left pane, click Tomcat Manager. c. Log in to the Tomcat Administrative Console using the following login credentials: 1. UserID: admin 2. Password: admin Installation and Configuration February

342 Chapter 5: Making changes to installed Avaya OA components d. In the Tomcat Web Application Manager page, check for: Display Name Stumbras Running true 342 Installation and Configuration February 2017

343 Chapter 6: Troubleshooting an installation This section provides some troubleshooting hints to help you get OA installed and running. You might do some troubleshooting using the Administration client interface. For more information, see the Administration Client Help. Following the suggestions in this section can usually help you determine the problem areas you must work on. For more help, contact Avaya Customer Support or your Avaya Professional Services representative. This section includes the following topics: Incorrect OS and database installation on page 343 Diagnosing installation problems on page 344 Installation failure after changing the domain name on page 344 Processes not running on page 345 Data not transferred or collected on page 345 Missing files on page 345 Subsystems not installed on page 345 Unable to install Report client files on page 346 Report access failure on page 346 Administration client authorization failures on page 347 Password changes on page 347 Display problems with AIX on page 347 Corruption in AIX terminal windows on page 348 Incorrect OS and database installation One of the most common causes of installation failure is improper setup of the operating system environment before attempting to install OA. Ensure that you verify that the customer has followed the steps outlined in Preparing for installation on page 15. You must install all supporting environment software in the proper order. Installation and Configuration February

344 Chapter 6: Troubleshooting an installation Diagnosing installation problems If you encounter difficulties with the OA installation, following these steps might help you find the cause of the trouble: 1. Access the OAInstall.log file. For Windows, this file is in %TEMP% during the installation, and after the server restarts in the %PABASE%. For Solaris, AIX, and RHEL this file is in /tmp during the installation, and in $PABASE after the installation. The location of the %TEMP% folder in Windows depends on how Windows was installed. 2. View the OAInstall.log file. This log file reports: Installed components. Errors encountered during installation. Rollbacks because of installation errors. If the log file information does not lead to a resolution of the difficulty, contact your Avaya planning and installation support representative or your Avaya Business Partner. Installation failure after changing the domain name The database software can no longer authenticate the owner of the database files and the folders during OA installation because of the following: The original installation of the database software is on a server using a Windows domain login (not a local administrator login). The change of the domain name of that server. The installation fails. To fix this problem, log in as a local administrator on the database server and reinstall the database software. For more information, see Avaya Operational Analyst Release 7.3.x Installation Planning and Prerequisites. To maintain your data, you must do a full backup, reinstall the database software, then restore the data. 344 Installation and Configuration February 2017

345 Processes not running For more information, see Avaya Operational Analyst Release 7.3.x Maintenance and Troubleshooting.. After you have reinstalled the database software, reinstall the OA software. For more information, see Installing Avaya OA components on a Windows platform on page 35. Processes not running Use the commands described in Avaya Operational Analyst Release 7.3.x Maintenance and Troubleshooting to start processes that might not be running. Data not transferred or collected If the data collection sources are not transferring data, or if the historical server is not collecting the data, use the dcstat command to check the forwarders and recorders. For more information, see Avaya Operational Analyst Release 7.3.x Maintenance and Troubleshooting. Missing files When attempting to run OA, if a window displays indicating that DLLs or other files are missing, you must repair the OA software. For more information, see Repairing Avaya OA components on page 260. For repair use the Feature Selection dialog box to select all components previously installed. Subsystems not installed When installing subsystems on a Windows server, the Windows Terminal Services feature might block the installation of certain subsystems, in particular, the Source-EC subsystem. Installation and Configuration February

346 Chapter 6: Troubleshooting an installation If you have installed the Source-EC subsystem on a server, but later determine the installation failed, reinstall the Source-EC subsystem. Ensure that you temporarily change the Terminal Services install option using the change user /install command. For more information, see Installing Avaya OA components on a Windows platform on page 35. Report client installation fails to work If you install the Report client files, but you cannot access any reports, perform the following: Verify that you have not installed the Report client files on a Microsoft Windows Server 2008 R2 (Standard and Enterprise edition) or Microsoft Windows Server 2012 Standard edition system. You cannot use this installation option. Ensure that the OA Reporting Client doesnt co-reside with other OA applications. For more information, see Avaya Operational Analyst Release 7.3.x Maintenance and Troubleshooting. Unable to install Report client files The IIS Lockdown tool might be the cause of why you cannot install the OA Report client files and JRE on reporting client systems. If the IIS Lockdown tool is on the server where the Report subsystem is and the URLScan option is enabled, remove the IIS Lockdown tool. Remove the IIS Lockdown tool before you try to install the Report client files onto the client systems. After you install all client systems, reinstall the IIS Lockdown tool onto the server where the Report subsystem is. Report access failure If you try to access reports and receive a Page Not Found, This page cannot be displayed, or other similar error, it might be that the Report subsystem has not been administered. To verify that the Report subsystem has been administered: 1. Start the Administration client. 2. Access the Subsystems page. 346 Installation and Configuration February 2017

347 Administration client authorization failures 3. Verify that there is an entry for a Report subsystem on the subsystem where you are attempting to run reports. If you try to access reports and the system rejects your login and password, or you receive a Forbidden error, it might be that the Historical subsystem is not operating or cannot be accessed over the network. Confirm that the Historical subsystem is operating correctly and that it can be accessed over the network. Verify that your user ID is a member of the Reports group. If you are getting Java errors, verify that the installation of the JRE and Report client support files. For more information, see Installing and testing the Report client on page 153. For more information, see Adding a Report subsystem on page 181 and the Administration Client Help on how to administer the Report subsystem and starting the web services. If you still cannot access reports, see Avaya Operational Analyst Release 7.3.x Maintenance and Troubleshooting. Administration client authorization failures If you cannot access the OA Administration client because of authorization failures, see Avaya Operational Analyst Security Guide on user ID and group creation and the guidelines. Password changes If you change database passwords external to OA, you might need to repair OA to reset the passwords. For more information, see Repairing Avaya OA components on page 260. Display problems with AIX When installing on AIX, you might have problems displaying the installation dialog boxes if you do not set the display environment of the monitor. Before you begin the install, enter: export DISPLAY=hostname:0.0 where hostname is the name of the server (uname -n) or the IP address of the server. Installation and Configuration February

348 Chapter 6: Troubleshooting an installation Corruption in AIX terminal windows During installation of OA on an AIX server, you might see intermittent errors when creating logical table spaces. These errors might note the tablespaces are too small, although you have set up the tablespaces to be larger than the minimum sizes. If this continues to happen, cancel the install, close the AIX terminal window, and then restart the installation in a new terminal window. Domain controller loses connection When adding, repairing, or upgrading OA components on a Windows system, you receive a message saying you are using an invalid user ID or invalid group ID. This message might happen because the system or domain server losing track of the system on where you are installing OA. To work around this problem on Windows 2008 R2: 1. From the Windows Desktop, right-click My Computer and select Properties. 2. Select the Computer Name tab. 3. Select Change. 4. Under Computer Name Changes, select Workgroup. 5. Enter the new work group. 6. Select OK. 7. Select Apply. 8. Choose a domain. 9. Select Apply. 10. Reboot the computer Installation and Configuration February 2017

349 Appendix A: Using latest version of Oracle JRE for Reporting Client for OA In OA 7.3.3, OA officially supports Oracle JRE 1.6.0_45 as the only JRE version for running OA 3D java based reports. The following must be installed on the user system for running the following 3D Reports. JRE version (1.6.0_45) OA Report supporting files The above files are present for download and installation on the OA Report page. Click the Install Reporting Support Files link to install the reporting support files. However, it may so happen that owing to corporate policies and/or security considerations, a higher version of JRE is mandated by the organization. This section provides information on running OA 3D reports using higher JRE version. The following JRE versions have been evaluated and found to be working: JRE 1.7 Update 76 JRE 1.8 Update 40 A user can attempt to follow the steps mentioned in this document for usage of any intermediate JRE versions so long as those JRE versions attempted for usage are forward compatible to the above evaluated versions. Security Restrictions introduced in JRE 1.7/1.8 Starting from JRE release 7u51 new security enhancements have been introduced to: Block self-signed and unsigned applets on high security setting Set the Permissions attribute for high security setting Warn users of missing Permissions attributes for medium security setting Installation and Configuration February

350 Appendix A: Using latest version of Oracle JRE for Reporting Client for OA For sites like OA Reporting that do not meet the above stringent criteria, there is way of how the RIA/Java applets can be accessed. With the Exception Site List feature end users can run Java applets and Java Web Start applications that do not meet the latest security requirements. Rich Internet Applications that are hosted on a site in the Exception Site List are allowed to run with the applicable security prompts. Future releases of OA will, however, address the above security restrictions introduced by newer JREs. JRE configuration changes required in order to run OA 3D report using higher version of JRE: 1. Microsoft Internet Explorer (32 bit) browser is launched in administrator mode. 2. The user accesses the Install Reporting Support Files link and successfully installs the JRE update 45 JRE on the desktop client system where OA Reports are accessed. 3. Using the Install Reporting Support Files link, the OA Install Reporting Client support files are also installed. Ensure the installation of the support files is successful. 4. For Microsoft Internet Explorer 11, the Report URL site must be added to the Compatibility View settings and also added to the trusted site list. 5. Try accessing the OA 3D reports and you should be able to successfully launch any OA 3D report. 6. Take a backup of the following files from the existing JRE 160_45 install: a. JAVA_HOME\lib\ext\in3d.jar b. JAVA_HOME\lib\security\java.security The JAVA_HOME is assumed to be the complete path of installation of JRE 1.6.0_45. Configuration changes for JRE Download and install the JRE from the Oracle download site. 2. Once the newer JRE installation is successful, copy the backed up file in3d.jar in the new JRE install location of the ext folder. 3. Open the java.security file of the 160_45 location and copy the following entry of type as part of the java.security file of the new JRE installation: policy.url.3=file:c:/progra~1/avaya/bi/cfg/javarpt.policy 4. After installation of the newer JRE, the JRE installer gives you an option to uninstall the older unsupported JRE version (JRE 160_45). The users can decide whether they want to maintain both the JREs or only have the desired/latest JRE. 5. Click Start > Control Panel. 6. In the Control Panel window, click Java icon. 7. In the Java Control Panel, click the Update table tab and clear the option to Check for Updates Automatically. 350 Installation and Configuration February 2017

351 Security Restrictions introduced in JRE 1.7/1.8 Installation and Configuration February

352 Appendix A: Using latest version of Oracle JRE for Reporting Client for OA Click the Java tab, and then click View. Ensure that as part of the User tab, 1.7 is listed as one of the JRE available for use. Select the Enable check box and click OK. 9. Click the Security tab and ensure the following: a. The Enable Java content in the browser option is selected. b. Select the appropriate security level. If you select a security level other than Medium (Least secure setting) Very High or High, then the OA Report URL (with port) has to be part of the exception list. This exception list is actually whitelisting specific sites. It facilitates accessing those specific sites and run Java applets that do not meet the latest security requirements. For more details see: exception_sitelist.xml c. To add sites to the Exception Site List on the Microsoft Windows system: a. Click Start > Control Panel. b. In the Control Panel window click Java. 352 Installation and Configuration February 2017

353 Security Restrictions introduced in JRE 1.7/1.8 c. In the Java Control Panel window, click Security tab. d. Click Edit Site List. The system displays the Exception Site List dialog box. e. Click Add. f. Add the site URL in the Location field. g. Click OK. d. You can also set the Security Level to Medium, which is the least secure setting. When you set the Security Level to Medium, all Java applications are allowed to run after presenting a security prompt. If Medium (Least secure setting) is selected then the OA Report URL (with port) need not be part of the exception list. Installation and Configuration February

354 Appendix A: Using latest version of Oracle JRE for Reporting Client for OA Open the Advanced tab and ensure the following: a. Under Default Java for browsers option set Microsoft Internet Explorer by default. b. Under Java Plug-in option ensure that the Enable the next-generation Java Plug-in (requires browser restart) is selected. 354 Installation and Configuration February 2017

355 Security Restrictions introduced in JRE 1.7/ Click OK and close the Java Control Panel. 12. Open Microsoft Internet Explorer and access the OA 3D reports. 13. When you access the OA 3D report, the system displays a security warning. Select I accept the risk and want to run the application and click Run to access the 3D report. Configuration changes for JRE Download and install the JRE from the Oracle download site. 2. After installing the newer JRE, copy the backed up file in3d.jar to the new JRE install location of the ext folder. 3. Open the java.security file of the 160_45 location and copy the entry of type as shown below as part of the java.security file of the new JRE installation.: Installation and Configuration February

356 Appendix A: Using latest version of Oracle JRE for Reporting Client for OA a. policy.url.3=file:c:/progra~1/avaya/bi/cfg/javarpt.policy 4. After installation of the newer JRE, the JRE installer provides an option to uninstall the older unsupported JRE version (JRE 160_45). It is up to the user to maintain both the JREs or only have the latest JRE installed. 5. Click Windows > Control Panel. 6. In the Windows Control Panel, Open the JCP or the Java Control Panel. 7. Click the Update table tab and clear the option to Check for Updates Automatically. 8. Click the Java tab. 9. Ensure that as part of the User tab, 1.8 is listed as one of the JRE available for use. Select the check box and click OK. 356 Installation and Configuration February 2017

357 Security Restrictions introduced in JRE 1.7/ Click the Security tab and ensure the following: a. The Enable Java content in the browser option is selected. b. Select the appropriate Security Level as per user s requirements, however ensure that the OA Report URL (with port) is added to the Exception site list. Installation and Configuration February

358 Appendix A: Using latest version of Oracle JRE for Reporting Client for OA Click on Advanced tab. 12. On the Advanced tab ensure that in the Default Java for browsers field, Microsoft Internet Explorer is selected. 13. Click OK and close the JCP. 14. Open Microsoft Internet Explorer browser and access the OA 3D reports. 15. When you access the OA 3D report, a security warning is displayed. Select the I accept the risk and want to run the application and click Run to access the 3D report. 358 Installation and Configuration February 2017

359 Security Restrictions introduced in JRE 1.7/1.8 Java Control Panel Security tab JRE 1.7.0_51 had a different version of Java Control Panel security user interface, wherein a slider is provided to select the appropriate security level instead of radio buttons. For more information on RIA security see: Installation and Configuration February

360 Appendix A: Using latest version of Oracle JRE for Reporting Client for OA Installation and Configuration February 2017

361 Appendix B: Changing the Cognos installation Normally, you can only install the Advanced Reports subsystem on the C: drive of a Windows server. This is also true for the Cognos software that is used with Advanced Reports. For Advanced reporting, Avaya OA uses COGNOS 7.4. COGNOS 7.4 runs only on the 32-bit Windows system and does not have a compatible version that can run on the 64-bit system. However, Avaya OA only supports Windows Server 2008 R2 and Windows Server 2012 R2. Therefore, you cannot use Advanced reporting on Windows Server 2008 R2, Windows Server 2012 R2, Solaris, or AIX. The Advanced Report sub system only functions on Microsoft Windows XP. Since, Microsoft Windows XP support is dropped in OA 7.3.3, Advanced Report sub system is no longer supported from OA onwards. This section describes how you can change the standard installation of Cognos to move the cubes to another drive instead of C: drive on a Windows server. See your Avaya services representative for support doing this procedure. This section includes the following topics: Prerequisites on page 361 Changing the Cognos installation on page 362 Prerequisites Before you begin this procedure, verify that you perform the following: You install the Cognos software in the standard location on the C: drive. You install the Advanced Reports subsystem on the same server. For more information, see Installing Avaya OA components on a Windows platform on page 35. You copy the reports folder and all that is in the folder to the new location. In the example in this section, drive R is being used. Installation and Configuration February

362 Appendix B: Changing the Cognos installation Changing the Cognos installation You use this procedure for modifying the Advanced reports that do not have a different database name other than the default database names. In this example, the drive being used for Cognos is named D and the drive used for the cubes is named R. This procedure sets up the OA Advanced Reports for Cognos to the following network folder: R:\oa advanced reports\reports\ To change the Cognos installation: 1. Open Impromptu Administrator. 2. Select Catalog > Databases. The Database Definition Manager dialog box displays. 3. Edit the database parameters to be able to connect to the databases. 4. Select OK. 362 Installation and Configuration February 2017

363 Changing the Cognos installation 5. Select Tools > Options and select the File Locations tab. 6. Set the above paths as needed. 7. Click OK when you finish setting the paths. 8. Using Catalog > Open, open the Catalog file (.cat file) for the following: R:\OA Advanced Reports\reports\cognos\Impromptu\CallCenterQ R:\OA Advanced Reports\reports\cognos\Impromptu\qrepository R:\OA Advanced Reports\reports\cognos\Impromptu\CustQ R:\OA Advanced Reports\reports\cognos\Impromptu\HRQ R:\OA Advanced Reports\reports\cognos\Impromptu\oadb 9. Connect to the database with the user ID and password. Installation and Configuration February

364 Appendix B: Changing the Cognos installation 10. Open each.imr file in the related application folder. For example, if you open the ccq.cat file, open each.imr file in the CallCenterQ folder and cancel out of any parameter prompts. See the following dialog box as an example: 364 Installation and Configuration February 2017

365 Changing the Cognos installation 11. Select the bitmap on each report, right-click the report, and select Properties. The Picture Properties dialog box displays. 12. Change the source path and select OK. Installation and Configuration February

366 Appendix B: Changing the Cognos installation 13. Select Report > General. The Report Properties dialog box displays. 14. Change the Catalog path and select OK. The following Impromptu message dialog box displays: 366 Installation and Configuration February 2017

367 Changing the Cognos installation 15. Select Yes. The following Impromptu message dialog box displays: 16. Select Yes. 17. Repeat Steps 10 through 16 for each.imr file in the appropriate folder. You might also open each.imr file in the folder and the appropriate.cat file opens. 18. For Impromptu files under cubes/xxx subfolders, perform one of the following: Open all.imr files with Impromptu Administrator and do a Save as to save each.imr file as a *.iqd file, overwriting the existing file. Use a text editor to edit the file paths in all *.iqd files. 19. Open Power Play Transformer. 20. Select Files > Preferences. Installation and Configuration February

368 Appendix B: Changing the Cognos installation 21. Select the Directories tab. 22. Set the above paths as needed. 23. Click OK when you finish setting the paths. 368 Installation and Configuration February 2017

369 Changing the Cognos installation 24. Open each MDL at the following locations: R:\OA Advanced Reports\reports\cognos\cubes\CallCenterQ R:\OA Advanced Reports\reports\cognos\cubes\contacts R:\OA Advanced Reports\reports\cognos\cubes\tasks R:\OA Advanced Reports\reports\cognos\cubes\CMS R:\OA Advanced Reports\reports\cognos\cubes\MMA The following is an example of the Data Sources dialog box: Installation and Configuration February

370 Appendix B: Changing the Cognos installation 25. For each MDL file, change Data Sources by right-clicking on the first one and selecting Properties. The Data Source - MDL_file dialog box displays: 26. Set the local data file parameter to the correct folder path, for example: r:\oa advanced reports\reports\cognos\cubes\callcenterq\ timeranges.iqd For multibyte (localized) versions of cubes, this example is: r:\oa advanced reports\reports\cognos\cubes\callcenterq\ timeranges.csv 370 Installation and Configuration February 2017

371 Changing the Cognos installation 27. Select OK. The following warning dialog box displays: 28. Select Yes. 29. Save the MDL file. Installation and Configuration February

372 Appendix B: Changing the Cognos installation 30. Right-click each Measure in each MDL file and select Properties. The properties dialog box displays. 31. If the Drill Through tab has an entry, you must change the path for each entry for every measure listed. Some might not have any entries in the Drill Through tab. For example, change to: R:\OA Advanced Reports\reports\cognos\Impromptu\CallCenterQ You have to change several entries in the MDL file manually as the entries are not user editable from the application. Use a text editor, such as Text Pad, to make these changes. 32. Open the MDL file in Powerplay Transformer. 33. Under the Run menu, run Generate Categories and the Update PowerCubes. 34. Open PowerPlay. 372 Installation and Configuration February 2017

373 Changing the Cognos installation 35. Go to File > Preferences and select the Directories tab. 36. Set the paths as appropriate for the reports on which you be working on. For example, R:\OA Advanced Reports\reports\cognos\PowerPlay\CallCenterQ R:\OA Advanced Reports\reports\cognos\PowerPlay\qrepository R:\OA Advanced Reports\reports\cognos\PowerPlay\tasks 37. Click OK when you finish. Installation and Configuration February