Avaya Operational Analystsupport.avaya.com/elmodocs2/qq/pdf/docs/oa71/whats… · · 2006-06-09What™s New in Operational Analyst 7.1 OA 7.1. Operational Analyst . Avaya .! 1 2

Avaya Operational AnalystRelease 7.1What�s New in Operational Analyst

07-600837Release 7.1

May 2006COMPAS ID 111077

© 2006 Avaya Inc. All Rights Reserved.

NoticeWhile reasonable efforts were made to ensure that the information in this document was complete and accurate at the time of printing, Avaya Inc. can assume no liability for any errors. Changes and corrections to the information in this document might be incorporated in future releases.

Documentation disclaimerAvaya Inc. is not responsible for any modifications, additions, or deletions to the original published version of this documentation unless such modifications, additions, or deletions were performed by Avaya. Customer and/or End User agree to indemnify and hold harmless Avaya, Avaya's agents, servants and employees against all claims, lawsuits, demands and judgments arising out of, or in connection with, subsequent modifications, additions or deletions to this documentation to the extent made by the Customer or End User.

Link disclaimerAvaya Inc. is not responsible for the contents or reliability of any linked Web sites referenced elsewhere within this documentation, and Avaya does not necessarily endorse the products, services, or information described or offered within them. We cannot guarantee that these links will work all the time and we have no control over the availability of the linked pages.

WarrantyAvaya Inc. provides a limited warranty on this product. Refer to your sales agreement to establish the terms of the limited warranty. In addition, Avaya�s standard warranty language, as well as information regarding support for this product, while under warranty, is available through the Avaya Support Web site:http://www.avaya.com/support

LicenseUSE OR INSTALLATION OF THE PRODUCT INDICATES THE END USER'S ACCEPTANCE OF THE TERMS SET FORTH HEREIN AND THE GENERAL LICENSE TERMS AVAILABLE ON THE AVAYA WEB SITE http://support.avaya.com/LicenseInfo/ ("GENERAL LICENSE TERMS"). IF YOU DO NOT WISH TO BE BOUND BY THESE TERMS, YOU MUST RETURN THE PRODUCT(S) TO THE POINT OF PURCHASE WITHIN TEN (10) DAYS OF DELIVERY FOR A REFUND OR CREDIT.Avaya grants End User a license within the scope of the license types described below. The applicable number of licenses and units of capacity for which the license is granted will be one (1), unless a different number of licenses or units of capacity is specified in the Documentation or other materials available to End User. "Designated Processor" means a single stand-alone computing device. "Server" means a Designated Processor that hosts a software application to be accessed by multiple users. "Software" means the computer programs in object code, originally licensed by Avaya and ultimately utilized by End User, whether as stand-alone Products or pre-installed on Hardware. "Hardware" means the standard hardware Products, originally sold by Avaya and ultimately utilized by End User.

License type(s)Concurrent User License (CU). End User may install and use the Software on multiple Designated Processors or one or more Servers, so long as only the licensed number of Units are accessing and using the Software at any given time. A "Unit" means the unit on which Avaya, at its sole discretion, bases the pricing of its licenses and can be, without limitation, an agent, port or user, an e-mail or voice mail account in the name of a person or corporate function (e.g., webmaster or helpdesk), or a directory entry in the administrative database utilized by the Product that permits one user to interface with the Software. Units may be linked to a specific, identified Server.Named User License (NU). Customer may: (i) install and use the Software on a single Designated Processor or Server per authorized Named User (defined below); or (ii) install and use the Software on a Server so long as only authorized Named Users access and use the Software. "Named User," means a user or device that has been expressly authorized by Avaya to access and use the Software. At Avaya's sole discretion, a "Named User" may be, without limitation, designated by name, corporate function (e.g., webmaster or helpdesk), an e-mail or voice mail account in the name of a person or corporate function, or a directory entry in the administrative database utilized by the Product that permits one user to interface with the Product. Shrinkwrap License (SR). With respect to Software that contains elements provided by third party suppliers, End User may install and use the Software in accordance with the terms and conditions of the applicable license agreements, such as "shrinkwrap" or "clickwrap" license accompanying or applicable to the Software ("Shrinkwrap License"). The text of the Shrinkwrap License will be available from Avaya upon End User�s request (see �Third-party Components" for more information).

Copyright Except where expressly stated otherwise, the Product is protected by copyright and other laws respecting proprietary rights. Unauthorized reproduction,

transfer, and or use can be a criminal, as well as a civil, offense under the applicable law.

Third-party componentsCertain software programs or portions thereof included in the Product may contain software distributed under third party agreements ("Third Party Components"), which may contain terms that expand or limit rights to use certain portions of the Product ("Third Party Terms"). Information identifying Third Party Components and the Third Party Terms that apply to them is available on the Avaya Support Web site:http://support.avaya.com/ThirdPartyLicense/

Preventing toll fraud"Toll fraud" is the unauthorized use of your telecommunications system by an unauthorized party (for example, a person who is not a corporate employee, agent, subcontractor, or is not working on your company's behalf). Be aware that there can be a risk of toll fraud associated with your system and that, if toll fraud occurs, it can result in substantial additional charges for your telecommunications services.

Avaya fraud interventionIf you suspect that you are being victimized by toll fraud and you need technical assistance or support, call Technical Service Center Toll Fraud Intervention Hotline at +1-800-643-2353 for the United States and Canada. For additional support telephone numbers, see the Avaya Support Web site:http://www.avaya.com/support

TrademarksAvaya, the Avaya logo, and COMPAS are either registered trademarks or trademarks of Avaya Inc. in the United States of America and/or other jurisdictions.All other trademarks are the property of their respective owners.

Downloading documentsFor the most current versions of documentation, see the Avaya Support Web site:http://www.avaya.com/support

COMPASThis document is also available from the COMPAS database. The COMPAS ID for this document is 111077.

Avaya supportAvaya provides a telephone number for you to use to report problems or to ask questions about your product. The support telephone number is 1-800-242-2121 in the United States. For additional support telephone numbers, see the Avaya Support Web site:http://www.avaya.com/support

http://www.avaya.com/support

http://www.avaya.com/support

http://www.avaya.com/support/

http://support.avaya.com/LicenseInfo/

http://support.avaya.com/ThirdPartyLicense/

http://www.avaya.com/support/

What�s New in OA Release 7.1 May 2006 3

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Purpose. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Related documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

What�s New in Operational Analyst 7.1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Upgrade paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Product interoperability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Interoperability with Interaction Center . . . . . . . . . . . . . . . . . . . . . . . . 11Interoperability with Call Management System . . . . . . . . . . . . . . . . . . . . 11

Aux Reason codes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Agent availability by channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Optional database management on Oracle . . . . . . . . . . . . . . . . . . . . . . . . 13Flexible JRE support for Report Client. . . . . . . . . . . . . . . . . . . . . . . . . . . 14Container ID in Administration Client . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Hardware and software requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Server machine hardware sizing . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Client software requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Server software requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Software required for the historical database and Historical subsystem servers 17Software required for Real-time servers . . . . . . . . . . . . . . . . . . . . . . 20Software required for report servers . . . . . . . . . . . . . . . . . . . . . . . . 20Software required for Source-CMS collection subsystem . . . . . . . . . . . . 22Software required for Source-EC (Event Collector) collection subsystem . . . 23Software required for Source-EC Bridge (Event Collector Bridge) collection subsystem23

Special notice about Windows Server 2003 SP1 . . . . . . . . . . . . . . . . . . . . . 24User documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Contents

Contents

4 What�s New in OA Release 7.1 May 2006


Preface

The section includes the following topics:

● Purpose on page 5

● Audience on page 5

● Related documents on page 6

PurposeThe purpose of this guide is to provide detailed information about Operational Analyst Release 7.1. This document describes functionality in OA 7.1 that is new or updated since OA 7.0.

AudienceThis guide is intended primarily for those who use Operational Analyst. You should use this guide as an information source for understanding the new and enhanced functionality available in OA 7.1.

Users of this document should have working knowledge of IC or CMS, or both, and how they interact with OA.

Preface


Related documentsThe following table lists all of the Avaya OA information, both documents and online help systems:

The following table lists Avaya IC information that may be helpful:

The Release.pdf file contains the latest notes about installation of OA components. Avaya recommends that you read these notes before installation.

After installation, you can view the release notes at:

● %PABASE%\doc\Release.pdf (Windows)

Title Number Compas ID

Avaya Operational Analyst 7.1 What�s New in Operational Analyst 07-600837 111077

Avaya Operational Analyst Release 7.1 Installation Planning and Prerequisites

07-600833 111073

Avaya Operational Analyst Release 7.1 Installation and Configuration 07-600834 111074

Avaya Operational Analyst Release 7.1 Maintenance and Troubleshooting

07-600835 111076

Avaya Operational Analyst Release 7.1 Reports Reference 07-600836 111075

Avaya Operational Analyst 7.1 Data API Utility 07-600838 115820

Avaya Operational Analyst 7.1 Administration Client Online Help See Administration client help or library CD-ROM

Avaya Operational Analyst 7.1 Basic Reports Online Help See Report client help

Data Model Help See product CD-ROM

Security Guide See product CD-ROM

Title Number Compas ID

Avaya Interaction Center Release 7.1 Installation Planning and Prerequisites

07-300568 113230

Avaya Interaction Center Release 7.1 Installation and Configuration 07-300569 113231

Avaya Interaction Center 7.1 Business Advocate Configuration and Administration

07-300574 113148

Related documents


● $PABASE/doc/Release.pdf (Solaris and AIX)

The default installation directories that represent %PABASE% and $PABASE are:

● c:\Program Files\Avaya\BI (Windows)

● /export/home/biadmin/BI (Solaris)

● /home/biadmin/BI (AIX)

Preface



What�s New in Operational Analyst 7.1

Avaya Operational Analyst Release 7.1 (OA 7.1) offers a number of enhancements to functionality provided by OA Release 7.0 and its successor Service Pack releases. This section contains an overview of the changes and additions you will find in OA 7.1, and information you need to successfully upgrade to the new version of the software.

This section includes the following topics:

● Upgrade paths on page 10

● Product interoperability on page 11

● Aux Reason codes on page 12

● Agent availability by channel on page 12

● Optional database management on Oracle on page 13

● Flexible JRE support for Report Client on page 14

● Container ID in Administration Client on page 14

● Hardware and software requirements on page 14

● User documentation on page 24



Upgrade pathsYou may upgrade to OA 7.1 from OA 7.0, OA 7.0.1, or OA 7.0.2 releases only. The following diagram illustrates the OA upgrade paths:

Upgrade instructions are detailed in Avaya Operational Analyst Release 7.1 Installation and Configuration.

Product interoperability


Note:Note: Instructions for upgrading to OA 6.1.3 from prior versions are available in

"Upgrading Avaya OA software" in Avaya Operational Analyst Release 6.1.3 Installation and Configuration.

Product interoperabilityOA 7.1 offers interoperability with numerous releases of Avaya Interaction Center (IC) and Avaya Call Management System (CMS). The following sections describe the interoperability between these products.

Interoperability with Interaction CenterThe following table shows the specifics of which IC and OA versions are certified by Avaya being as interoperable and supported combinations.

Interoperability with Call Management SystemThe following table shows the interoperability of recent releases of OA with recent releases of CMS.

OA 6.1.3 OA 6.1.3 SP 1

OA 6.1.3 SP 2

OA 7.0 OA 7.0.1 OA 7.0.2 OA 7.1

IC 6.1.3 X X X X

IC 6.1.4 X X

IC 6.1.5 X

IC 7.0 X X

IC 7.0.1 X

IC 7.0.2 X

IC 7.1 X



Aux Reason codesPrior to OA 7.1, OA provided the capability to report the current state of an agent, and the amount of time an agent has been in a particular state for a given interval. This ability to track state changes also applies to the On Break or Aux Work state. You may want to know why an agent changes state into the Aux Work state.

OA 7.1 adds the ability to define Aux Reason codes to track not only the Aux Work state and duration of time the agent is in that Aux Work state, but also the reason an agent changed state into the Aux Work state. For example, you might define codes to indicate that an agent is on break, attending a training class, or any other reason that makes sense in your business scenario.

See Operational Analyst Release 7.1 Reports Reference for details about creating reports that use Aux Reason codes.

Agent availability by channelThe agent availability reporting provided by OA 7.0 is not associated with a specific channel (Voice, Chat, Email), but rather overall agent availability. OA 7.1 adds reporting on agent availability by channel. This allows you to utilize the availability algorithms supported by IC: agent-based load and channel-based load.

OA 6.1.3 and OA 6.1.3 SP1

OA 6.1.3 SP2 OA 7.0 and OA 7.0.1

OA 7.0.2 OA 7.1

CMS 9 X X X X X

CMS 11 X X X X X

CMS 12 X X X X X

CMS 13 Non-expanded Aux Codes

only

X X X

CMS 13.1

Non-expanded Aux Codes

only

X X X

Optional database management on Oracle


Agent-based load: This allows you to specify the number of contacts used to determine the availability of an agent. For example, consider an agent availability of 2. If an agent is handling two contacts, perhaps one email and one call, the agent is considered unavailable to handle additional contacts.

Channel-based load: This allows you to specify a number of contacts by channel to determine the agent availability. For example, you might set the voice channel load to 1 and the email channel load to 2. If an agent is handling one call and one email, the agent is considered unavailable for the voice channel, but is available for the email channel.

See Operational Analyst Release 7.1 Reports Reference for details about Agent Availability by Channel reports.

Optional database management on OracleOA 7.1 enhances flexibility in environments where the customer has a database administrator (DBA). Prior releases of OA did not require DBA expertise to create, configure, and maintain a database. Although smaller customers without DBA expertise may prefer this turn-key approach, it is not compatible in larger customer environments where a DBA manages the OA database as part of their larger data environment.

For all OA-supported databases, the OA installation requires a DB Administrator interface to complete database setup. With OA 7.1, this DB Administrator user can be any user with DBA privileges, rather than the standard database administrator that OA has defaulted to in previous releases:

● sys (Oracle)

● sa (MSSQL)

● db2inst1 (DB2)

For those customers who use the Oracle database, OA 7.1 allows the DBA to:

● Run SQL scripts for Oracle database installation. This replaces the automated database setup during OA installation, allowing DBA control of database setup.

● Manually create a new Oracle database user and generate private synonyms for each OA table/view in the schema for that new user. This Oracle database user replaces the OA database user as the OA database interface.

● Revoke these Oracle system privileges from the OA database user:

- ANALYZE ANY- UNLIMITED TABLESPACE

● Remove the Oracle ANALYZE TABLES task from the set of tasks performed by OA DBCheck.



See Operational Analyst Release 7.1 Installation Planning and Prerequisites for information about manually managing your Oracle database.

Flexible JRE support for Report ClientOA 7.1 Report Client now supports JRE versions 1.4.2_08, 1.4.2_10 and 1.5.0_06.

The Avaya Operational Analyst 7.1 Basic Reporting Client requires two components, the Java 2 Runtime Environment (JRE) and the Reporting Client Support files. JRE 1.4.2_08 is the official version to run the graphical reports, and JRE 1.4.2_10 and JRE 1.5.0_06 are also supported. You can have any of these JRE installed on your machine.

If you have a later version of JRE installed on your machine, do not install an earlier version on top of the later version because doing so might leave your machine in an unstable state. For example, if JRE 1.5.0_06 is installed, do not remove it and install JRE 1.4.2_08.

Note:Note: If your system has applications that use an existing JRE, installing a new version

of JRE could cause adverse effects to those applications. Those applications may need to be re-installed.

Container ID in Administration ClientIn OA 7.1 the Administration Client Container Profiles screen shows the container ID appended to the container name. For example, if the container name is AgentStateCntr and the associated container ID is 2, then on the Container Profile screen the container is shown as AgentStateCntr(2).

Hardware and software requirementsThis section provides an overview of the OA 7.1 hardware and software requirements. In general, OA 7.1 drops support for:

● Windows 2000 Server

Note:Note: Windows 2000 support for Administration Client and Report Client continues in

OA 7.1.

● Solaris 8

Hardware and software requirements


Note:Note: OA continues support for CMS V9 running on Solaris 8.

● AIX 5.1

● DB2 V7.2

● Oracle 8i

● Java Runtime Environment (JRE) 1.3.1_06

and adds support for

● AIX 5.3

● Oracle 10g

● DB2 V8.2 (64-bit version)

● JRE 1.4.2_08

● JRE 1.4.2_10

● JRE 1.5.0_06

Full details about OA 7.1 hardware and software support are available in Operational Analyst Release 7.1 Installation Planning and Prerequisites.


● Server machine hardware sizing on page 15

● Client software requirements on page 16

● Server software requirements on page 17

Server machine hardware sizingThe OA server software can run on the following machines:

● Windows Server 2003 (except SP1)

● Solaris 9

● AIX 5.2

● AIX 5.3

The hardware requirements for servers depend upon the deployment of an Avaya OA system, the volume of contacts in the contact center, and performance requirements. For assistance with sizing an OA configuration, contact your Avaya representative or Avaya Business Partner representative.

Note:Note: When OA-related software is being installed on Avaya IC machines, the machine

must support the minimum requirements for Avaya IC as defined in Avaya Interaction Center Release 7.1 Installation Planning and Prerequisites.



Client software requirementsThe minimum software requirements for a desktop PC running OA reports or using the Administration client are listed in the following table:

CAUTION:!

CAUTION: The Report client software must not be installed on an Avaya OA or Avaya IC server machine. Running reports on a server machine can adversely affect the performance of the server.

Server software requirementsThis section outlines the generic software requirements for OA components. This information was complete and accurate at the time of publication. The actual installation steps for each software package may vary depending upon the version of the software media being used and other site-specific factors.

Component Minimum requirement

Operating system1

1. You cannot install and operate OA client software (Administration client or the Report client) on a Windows Server 2003 server.

Windows 2000 Professional, SP4orWindows XP Professional (32-bit), SP2

Web browser Internet Explorer 5.5 SP2 or later (for Windows 2000)orInternet Explorer 6.0 SP1 or later (for Windows XP)

JRE2

2. Avaya advises that OA 7.1 does not work with versions of JRE other than those versions specifically listed here.

Java Runtime Environment 1.4.2_08orJava Runtime Environment 1.4.2_10 (Reporting Client only)orJava Runtime Environment 1.5.0_06 (Reporting Client only)



The following sections detail the OA software infrastructure required for each OA subsystem or client package. This information is intended only for reference. Deployment of software components may vary depending on your system configuration and performance requirements. The version numbers associated with the supporting applications are specific to this release of OA.


● Software required for the historical database and Historical subsystem servers on page 17

● Software required for Real-time servers on page 20

● Software required for report servers on page 20

● Software required for Source-CMS collection subsystem on page 22

● Software required for Source-EC (Event Collector) collection subsystem on page 23

● Software required for Source-EC Bridge (Event Collector Bridge) collection subsystem on page 23

Software required for the historical database and Historical subsystem servers

The software required for machines with the historical database and the Historical subsystem depends on whether:

● the server machine has the historical database coresident on the same machine with the Historical subsystem (Historical subsystem coresident with the historical database on page 18), or

● the historical database is on a dedicated (back-end) machine and the Historical subsystem is on a separate machine with other OA software (Historical subsystem not coresident with the historical database on page 18).

Since OA 7.1 supports only certain combinations of operating systems and databases, these combinations are explained in Supported database management systems on page 19.

! Important:Important: The historical database cannot be coresident with any Avaya IC components.

Only OA components, typically the Historical subsystem, are ever installed on the same server with the historical database.

Historical subsystem coresident with the historical database: The following table lists the software required on a server machine when the historical database is coresident on the same machine with the Historical subsystem.



! Important:Important: See Supported database management systems on page 19 for allowable

operating system and database combinations.

Historical subsystem not coresident with the historical database: The following table lists the software required on a server machine when the historical database is not coresident on the same machine with the Historical subsystem (that is, the historical database is located on a dedicated, back-end database server machine).

Component Windows Solaris AIX

Operating system Windows Server 2003 (Standard or Enterprise Edition)1

Solaris 9 with Patch 111711-11 or later

AIX 5.2L Maintenance Level 4 with fileset xlc.rte.aix50.may2005.ptf orAIX 5.3 with fileset xlc.rte.aix50.may2005.ptf

Time synchronization utility

For time synchronization software requirements, see Appendix A: Time synchronization in Operational Analyst 7.1 Installation Planning and Prerequisites.

Historical database Microsoft SQL Server 2000 SP3a (Standard or Enterprise Edition, 32-bit version)orOracle 9.2.0 Patch 4.0 (Standard or Enterprise Edition, 32-bit version)orOracle 10g

Oracle 9i (32 bit)orOracle 10g (64 bit)

IBM DB2 8.1, FP5 Enterprise Edition (32-bit version)orIBM DB2 8.2 Enterprise Edition (32-bit or 64-bit version)

1. OA 7.1 supports Windows Server 2003 SP1 on either Standard or Enterprise edition with the SYN attack workaround. For details see Special notice about Windows Server 2003 SP1 on page 24.



! Important:Important: See Supported database management systems on page 19 for allowable

operating system and database combinations.

Supported database management systems: The following table describes the operating system required for each supported database management system.




AIX 5.2L Maintenance Level 4 with fileset xlc.rte.aix50.may2005.ptforAIX 5.3 with fileset xlc.rte.aix50.may2005.ptf



Historical database Microsoft SQL Server 2000 SP3a client (Standard or Enterprise Edition, 32-bit version)orOracle 9.2.0 Patch 4.0 client (Standard or Enterprise Edition, 32-bit version)orOracle 10g

Oracle 9i (32 bit)orOracle 10g (64 bit)

IBM DB2 8.1, client Enterprise Edition (32-bit version)orIBM DB2 8.2 client Enterprise Edition (32-bit version)


Server operating

system

Database management system

Windows SQL 2000

Oracle DB2

9i 10g Version 8.1 Version 8.2

Windows 2003 Yes Yes Yes No No

Solaris 9 No Yes Yes No No



Software required for Real-time servers

The following table lists the software required on real-time server machines when using the Real-time subsystem.

Software required for report servers

This section provides the software required for report server machines, both Basic and Tabular Report servers and Advanced Report servers.


● Basic Report and Tabular Report server on page 21

● Advanced Report server on page 21

AIX 5.2L No No No Yes Yes

AIX 5.3 No No No Yes Yes

Server operating

system

Database management system

Windows SQL 2000

Oracle DB2

9i 10g Version 8.1 Version 8.2


Operating system

Windows Server 2003 (Standard or Enterprise Edition)1






Real-time database

TimesTen 5.1.34 Real-time Database (embedded with OA software)





Basic Report and Tabular Report server: The following table lists the software required on Basic Report server machines when using the Report subsystem.

Advanced Report server: The following table lists the software required on Advanced Report server machines when using the Advanced Report subsystem.

Note:Note: The Advanced Report subsystem can be installed only on machines with

Windows server operating system. The Advanced Report subsystem is not supported on Solaris or AIX.

Component Windows1

1. Accessing reports using a Web browser on a Windows server is not supported. You must access the reports from a client PC.

Solaris AIX

Operating system







Web server Microsoft IIS 5.0 for Windows 2000 (installed when the OS is installed)orMicrosoft IIS 6.0 for Windows 2003 (must be installed separately from the OS)

Sun Java System Web Server 6.1 SP1

IBM WebSphere Application Server 6.0, which includes IBM HTTP Server 6.0

Component1 Windows

Operating system


Browser (optional)3

Internet Explorer 6.0 SP1 or later, or Netscape 4.76 or later



Software required for Source-CMS collection subsystem

The following table lists the software required for Avaya CMS server machines (Solaris only) when OA is used to collect data from the CMS.

Cognos software4

Cognos PowerPlay Transformation Server, Enterprise or Standard edition, Version 7.3, MR1

Cognos Impromptu Administrator, Enterprise or Standard edition, Version 7.3, MR15

Cognos Impromptu Web Reports for Windows, Enterprise or Standard edition, Version 7.3, MR1 (optional)3

Cognos PowerPlay Enterprise Server, Enterprise or Standard edition, Version 7.3, MR1 (optional)3 5

1. This table shows the minimum requirements known at the time of publication for software used to support the Cognos software. For the latest requirements, see http://support.cognos.com/support/products/software_environments.html.


3. Required only when Web support is needed.

4. The Cognos software is shipped with the Avaya OA software on a separate CD-ROM.

5. To support multibyte report data in OA 7.1 for languages that are not supported by Impromptu Administrator Version 7.x, install the proper localized multibyte version of Impromptu Administrator Version 6.3. If the language you need is still not available in Version 6.3, install the multibyte English version. Note that Impromptu Administrator 6.3 will not support an Oracle 9i database.

Component1 Windows

Component Solaris

Operating system Solaris 8 with patch 108434-18 (CMS R3V9 and CMS R3V11)orSolaris 9 (CMS R12, CMS R13 and CMS R13.1)

http://support.cognos.com/support/products/software_environments.html

http://support.cognos.com/support/products/software_environments.html



Software required for Source-EC (Event Collector) collection subsystem

The following table lists the software required when the Source-EC (Event Collector) subsystem is installed on an Avaya IC machine.

Software required for Source-EC Bridge (Event Collector Bridge) collection subsystem

The following table lists the software required when the Source-EC Bridge (Event Collector Bridge) subsystem is installed on an Avaya IC machine where Avaya Business Advocate is already installed.

Note:Note: The Source-EC Bridge subsystem can only be installed on machines with

Windows server operating system. The Source-EC Bridge is not supported on Solaris or AIX.








Component Windows



XML parser Microsoft XML Parser Version 3.0 SP1 or later2

Time synchronization utility For time synchronization software requirements, see Appendix A: Time synchronization in Operational Analyst 7.1 Installation Planning and Prerequisites.



Special notice about Windows Server 2003 SP1In some cases, upgrading Windows Server 2003 to Windows Server 2003 SP1 causes OA processes to fail to start. When this situation occurs, the Event Viewer contains messages indicating OA_startup failed.

The cause of this problem is SYN Attack Protection that is included in Windows Server 2003 SP1. SYN Attack Protection is designed to protect servers that are openly available on the internet from malicious attacks for server control. You should always position your OA servers behind your firewall to prevent open internet availability. If you follow this suggestion, you can safely disable SYN Attack Protection on your OA servers.

To disable SYN Attack Protection:

1. At a Windows command prompt run regedit.

2. Expand HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Tcpip\Parameters

3. Right click and add a new DWORD value parameter.

4. Rename the new parameter to SynAttackProtect.

5. Set the parameter value to 0.

6. Exit the Registry Editor.

7. Restart the OA server.

User documentationAll OA user documentation is updated for OA 7.1, including the documentation CD-ROM.

The documentation CD-ROM features an HTML-based library of all OA 7.1 documents, allowing cross-document searching. The library runs in a standard Microsoft Internet Explorer browser, providing navigation aids and hyperlinking within and between documents.

Should you desire to print a document (or a section of a document) you can select a link available on the title page of each document to open the PDF version of the document. Once the PDF document is open, you may print individual sections or the complete document.

The documents included in the OA 7.1 documentation library CD-ROM are:

● What�s New in Avaya Operational Analyst Release 7.1

2. The required XML Parser is provided automatically when Internet Explorer 6.0 SP1 or later is installed on the server.

User documentation


● Avaya Operational Analyst Release 7.1 Installation Planning and Prerequisites

● Avaya Operational Analyst Release 7.1 Installation and Configuration

● Avaya Operational Analyst Release 7.1 Maintenance and Troubleshooting

● Avaya Operational Analyst Release 7.1 Reports Reference

● Avaya Operational Analyst Release 7.1 Data API Utility

● Avaya Operational Analyst Release 7.1 Administration Client Online Help (PDF format only)




Index

Index

AAbout Avaya Operational Analyst Release 7.0 . . . . . 5Advanced Report server . . . . . . . . . . . . . . 21

CClient software requirements . . . . . . . . . . . . 16

HHardware and software requirements . . . . . . . . 14historical server

coresident database . . . . . . . . . . . . . . 18without coresident database . . . . . . . . . . . 18

Historical subsystemcoresident with the historical database . . . . . . 18not coresident with the historical database . . . . 18

IIntended users of this document . . . . . . . . . . . 5

PPreface . . . . . . . . . . . . . . . . . . . . . . . 5Purpose of this document . . . . . . . . . . . . . . 5

RRelated documentation. . . . . . . . . . . . . . . . 6report servers . . . . . . . . . . . . . . . . . . . 21

SSafety labels. . . . . . . . . . . . . . . . . . . . . 6Server machine hardware sizing . . . . . . . . . . 15Server software requirements. . . . . . . . . . . . 17software

required for historical servers . . . . . . . . . . 17required for Real-time servers . . . . . . . . . . 20required for report servers . . . . . . . . . . . . 20required for source-CMS collection subsystem . . 22required for source-EC (Event Collector) collection

subsystem . . . . . . . . . . . . . . . . . . 23

required for Source-EC Bridge (Event Collector Bridge) collection subsystem . . . . . . . . . . . . . . 23

Software requirements . . . . . . . . . . . . . . . 14

UUpgrade path . . . . . . . . . . . . . . . . . . . 10User documentation . . . . . . . . . . . . . . . . 24


Index

Documents

Avaya Operational Analystsupport.avaya.com/elmodocs2/qq/pdf/docs/oa71/whats… · · 2006-06-09What™s New in Operational Analyst 7.1 OA 7.1. Operational Analyst . Avaya .! 1 2