Avaya Agile Communication Environment Web Browser and Office Add-ins Application Fundamentals

Avaya Agile Communication Environment Web Browser and Office Add-ins Application Fundamentals Release 2.3.2 NN10850-031, 05.02 March 2011

2011 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 by Avaya in varying mediums which may include product information, operating instructions and performance specifications that Avaya generally makes available to users of its 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 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 Web sites 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 its Hardware and Software ( Product(s) ). Refer to your sales agreement to establish the terms of the limited warranty. In addition, Avaya s standard warranty language, as well as information regarding support for this Product while under warranty is available to Avaya customers and other parties through the Avaya Support Web site: http://support.avaya.com. Please note that if you acquired the Product(s) from an authorized Avaya reseller outside of the United States and Canada, the warranty is provided to you by said Avaya reseller and not by Avaya. Licenses THE SOFTWARE LICENSE TERMS AVAILABLE ON THE AVAYA WEBSITE, HTTP://SUPPORT.AVAYA.COM/LICENSEINFO/ ARE APPLICABLE TO ANYONE WHO DOWNLOADS, USES AND/OR INSTALLS AVAYA SOFTWARE, PURCHASED FROM AVAYA INC., ANY AVAYA AFFILIATE, OR AN AUTHORIZED AVAYA RESELLER (AS APPLICABLE) UNDER A COMMERCIAL AGREEMENT WITH AVAYA OR AN AUTHORIZED AVAYA RESELLER. UNLESS OTHERWISE AGREED TO BY AVAYA IN WRITING, AVAYA DOES NOT EXTEND THIS LICENSE IF THE SOFTWARE WAS OBTAINED FROM ANYONE OTHER THAN AVAYA, AN AVAYA AFFILIATE OR AN AVAYA AUTHORIZED RESELLER; AVAYA RESERVES THE RIGHT TO TAKE LEGAL ACTION AGAINST YOU AND ANYONE ELSE USING OR SELLING THE SOFTWARE WITHOUT A LICENSE. BY INSTALLING, DOWNLOADING OR USING THE SOFTWARE, OR AUTHORIZING OTHERS TO DO SO, YOU, ON BEHALF OF YOURSELF AND THE ENTITY FOR WHOM YOU ARE INSTALLING, DOWNLOADING OR USING THE SOFTWARE (HEREINAFTER REFERRED TO INTERCHANGEABLY AS YOU AND END USER ), AGREE TO THESE TERMS AND CONDITIONS AND CREATE A BINDING CONTRACT BETWEEN YOU AND AVAYA INC. OR THE APPLICABLE AVAYA AFFILIATE ( AVAYA ). Avaya grants End User a license within the scope of the license types described below. The applicable number of licenses and units of capacity for which the license is granted will be one (1), unless a different number of licenses or units of capacity is specified in the Documentation or other materials available to End User. Designated Processor means a single stand-alone computing device. Server means a Designated Processor that hosts a software application to be accessed by multiple users. Software means the computer programs in object code, originally licensed by Avaya and ultimately utilized by End User, whether as stand-alone Products or pre-installed on Hardware. Hardware means the standard hardware originally sold by Avaya and ultimately utilized by End User. License types Designated System(s) License (DS). End User may install and use each copy of the Software on only one Designated Processor, unless a different number of Designated Processors is indicated in the Documentation or other materials available to End User. Avaya may require the Designated Processor(s) to be identified by type, serial number, feature key, location or other specific designation, or to be provided by End User to Avaya through electronic means established by Avaya specifically for this purpose. Concurrent User License (CU). End User may install and use the Software on multiple Designated Processors or one or more Servers, so long as only the licensed number of Units are accessing and using the Software at any given time. A Unit means the unit on which Avaya, at its sole discretion, bases the pricing of its licenses and can be, without limitation, an agent, port or user, an e-mail or voice mail account in the name of a person or corporate function (e.g., webmaster or helpdesk), or a directory entry in the administrative database utilized by the Software that permits one user to interface with the Software. Units may be linked to a specific, identified Server. Database License (DL). End User may install and use each copy of the Software on one Server or on multiple Servers provided that each of the Servers on which the Software is installed communicate with no more than a single instance of the same database. CPU License (CP). End User may install and use each copy of the Software on a number of Servers up to the number indicated by Avaya provided that the performance capacity of the Server(s) does not exceed the performance capacity specified for the Software. End User may not re-install or operate the Software on Server(s) with a larger performance capacity without Avaya's prior consent and payment of an upgrade fee. Named User License (NU). End User may: (i) install and use the Software on a single Designated Processor or Server per authorized Named User (defined below); or (ii) install and use the Software on a Server so long as only authorized Named Users access and use the Software. Named User, means a user or device that has been expressly authorized by Avaya to access and use the Software. At Avaya's sole discretion, a Named User may be, without limitation, designated by name, corporate function (e.g., webmaster or helpdesk), an e-mail or voice mail account in the name of a person or corporate function, or a directory entry in the administrative database utilized by the Software that permits one user to interface with the Software. Shrinkwrap License (SR). Customer may install and use the Software in accordance with the terms and conditions of the applicable license agreements, such as shrinkwrap or clickthrough license accompanying or applicable to the Software ( Shrinkwrap License ). (see Third-party Components for more information). Copyright Except where expressly stated otherwise, no use should be made of materials on this site, the Documentation, Software, or Hardware provided by Avaya. All content on this site, the documentation 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 2 Web Browser and Office Add-ins Application Fundamentals March 2011

the express written consent of Avaya can be a criminal, as well as a civil offense under the applicable law. Third-party components Certain software programs or portions thereof included in the Product may contain software distributed under third party agreements ( Third Party Components ), which may contain terms that expand or limit rights to use certain portions of the Product ( Third Party Terms ). Information regarding distributed Linux OS source code (for those Products that have distributed the Linux OS source code), and identifying the copyright holders of the Third Party Components and the Third Party Terms that apply to them is available on the Avaya Support Web site: http://support.avaya.com/copyright. Preventing Toll Fraud Toll fraud is the unauthorized use of your telecommunications system by an unauthorized party (for example, a person who is not a corporate employee, agent, subcontractor, or is not working on your company's behalf). Be aware that there can be a risk of Toll Fraud associated with your system and that, if Toll Fraud occurs, it can result in substantial additional charges for your telecommunications services. Avaya 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 +1-800-643-2353 for the United States and Canada. For additional support telephone numbers, see the Avaya Support Web site: http://support.avaya.com. Suspected security vulnerabilities with Avaya products should be reported to Avaya by sending mail to: securityalerts@avaya.com. Trademarks The trademarks, logos and service marks ( Marks ) displayed in this site, the Documentation and Product(s) provided by Avaya are the registered or unregistered Marks of Avaya, its affiliates, 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 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. Avaya Aura is a registered trademark of Avaya Inc. Avaya ACE is a registered trademark of Avaya Inc. All non-avaya trademarks are the property of their respective owners, and Linux is a registered trademark of Linus Torvalds. Downloading Documentation For the most current versions of Documentation, see the Avaya Support Web site: http://support.avaya.com. Contact Avaya Support Avaya provides a telephone number for you to use to report problems or to ask questions about your Product. The support telephone number is 1-800-242-2121 in the United States. For additional support telephone numbers, see the Avaya Web site: http://support.avaya.com. Web Browser and Office Add-ins Application Fundamentals March 2011 3

4 Web Browser and Office Add-ins Application Fundamentals March 2011

Contents Chapter 1: New in this release...7 Features...7 AIE integration...7 Communicator Add-in integration...7 Other changes...7 Chapter 2: Introduction...9 Avaya ACE documentation...9 Avaya ACE professional services and support...10 Navigation...11 Chapter 3: Overview...13 Add-in applications...13 Web Browser Add-in application...13 Office Add-in application...13 Hot Desking integration...14 Communicator Add-in integration...14 Authorization application...15 Configurator...15 Web Browser Add-in install package...16 Office Add-in install package...17 Chapter 4: System requirements...19 Avaya ACE requirements...19 AIE requirements...19 Configurator requirements...20 Web Browser Add-in requirements...20 Office Add-in requirements...21 Service provider requirements...22 Web services requirements...22 Chapter 5: Building the install packages...23 Configuring the Authorization application...25 Installing the Configurator...26 Building the Web Browser Add-in install package...27 Building the Office Add-in install package...28 Configuring DCE authorization...29 Adding users to the Web Browser Add-in user group...30 Adding users to the Office Add-in user group...31 Web Browser and Office Add-ins Application Fundamentals March 2011 5

6 Web Browser and Office Add-ins Application Fundamentals March 2011

Chapter 1: New in this release The following sections detail what's new in Avaya Agile Communication Environment Web Browser and Office Add-ins Application Fundamentals (NN10850-031) for Release 2.3.2. Features The following features are new in this release: AIE integration on page 7 Communicator Add-in integration on page 7 AIE integration The Avaya ACE Application Integration Engine (AIE) now hosts the Web Browser and Office Add-in applications. The Configurator uses the AIE configuration details and the Authorization application on the AIE to build the install packages and set up the permissions for users to use the Web Browser and Office Add-in applications. Communicator Add-in integration The Web Browser and Office Add-in applications can now integrate with the Avaya ACE Communicator Add-in. As a result, users can make Office Communicator calls directly from web pages and Microsoft Office applications. Other changes There are no other changes at this time. Web Browser and Office Add-ins Application Fundamentals March 2011 7

New in this release 8 Web Browser and Office Add-ins Application Fundamentals March 2011

Chapter 2: Introduction Avaya Agile Communication Environment Web Browser and Office Add-ins Application Fundamentals (NN10850-031) provides the information needed to configure and build the application install packages for the Avaya Agile Communication Environment (ACE) Web Browser and Office Add-ins. Avaya ACE documentation Before using Avaya ACE, familiarize yourself with the following documentation resources. Avaya ACE documentation These documents provide information on Avaya ACE fundamentals, planning, software ordering, installation, Avaya and third-party system solution integration, web service application programming interfaces (APIs), administration, security, fault and performance management, troubleshooting, and core applications/apis delivered with the base software (Personal Assistant, Message Drop and Blast API). Avaya ACE application documentation The application documentation includes information on the planning, installing, administration, and use of the Application Integration Engine (AIE) platform and the applications it hosts, Microsoft and IBM desktop integration solutions, and all other prepackaged Avaya ACE applications. Avaya ACE Release Notes The Avaya ACE release notes describe operational considerations for a specific release of Avaya ACE. You can download this document from avaya.com/support. It is important to carefully review the release notes for the Avaya ACE release you support prior to a software install or upgrade. In addition, this document is a helpful reference for the ongoing support and use of Avaya ACE. Obtaining documents All Avaya ACE documentation is available from the Avaya support web site at https:// support.avaya.com. Avaya ACE documentation is available - on the Avaya ACE Server disk - from the Avaya ACE GUI Help menu Web Browser and Office Add-ins Application Fundamentals March 2011 9

Introduction - on the Avaya ACE server under the Linux folder /opt/avaya/ace/doc/ntp or under the Windows folder \Program Files\Avaya\Avaya ACE\ace\doc\NTP. Avaya ACE application documentation is available - on the Avaya ACE Applications disk - from the AIE GUI Help menu (for applications hosted through the AIE) Avaya ACE professional services and support Avaya ACE combines industry-leading consulting and design services with the right mix of custom development and communications integration capabilities, providing communications solutions that meet business needs now and in the future. Consulting and solution design: Help customers understand and design communications solutions holistically, ensuring all elements of the solution are addressed and aligned. Solution development and customization: Ensure the enterprise's unique requirements are met. Solution integration and implementation: Ensure the solution is deployed and integrated within the network and communications infrastructure and applications effectively, to achieve organizational and business goals. Project management and ongoing solution maintenance: Help enterprises manage and maintain their network and communications infrastructure. Business optimization: Ensure the deployed solution delivers maximum performance. Avaya Global Services Avaya Global Services delivers world-class support in three areas: Avaya Professional Services, Avaya Support Services, and Avaya Operations Services. Avaya Professional Services Avaya Professional Services consultants are technically proficient, possess strong business acumen and have developed vertical industry specialization to help you address the challenges of today s converged voice, video and data communications environments. At the same time, we actively help you look for ways to optimize your communications environment to better enable your people, increase your business agility, and drive costs out of your operations. Avaya Support Services Avaya Support Services are backed by global resources, including more than 5,800 industrycertified service desk and backbone engineers and 34 regional network operations centers delivering 24x7 monitoring, diagnostics and problem resolution, as well as support in 14 languages. Avaya Operations Services Avaya Operations Services are available for customers that want to out-task the proactive management and monitoring of their communications infrastructure. These services can be 10 Web Browser and Office Add-ins Application Fundamentals March 2011

Navigation delivered by Avaya directly or may be private-labeled and co-delivered by Avaya authorized partners. Navigation Overview on page 13 System requirements on page 19 Building the install packages on page 23 Web Browser and Office Add-ins Application Fundamentals March 2011 11

Introduction 12 Web Browser and Office Add-ins Application Fundamentals March 2011

Chapter 3: Overview The following sections provide an overview of the Avaya Agile Communication Environment (ACE) Web Browser and Office Add-in applications and conceptual information to help you build the install packages for the Web Browser and Office Add-ins to deploy to users. Navigation Add-in applications on page 13 Authorization application on page 15 Configurator on page 15 Add-in applications See the following sections for a description of the Avaya ACE Web Browser and Office Addins as well as the Avaya ACE Hot Desking application and the Avaya ACE Communicator Addin which can integrate with the add-in applications: Web Browser Add-in application on page 13 Office Add-in application on page 13 Hot Desking integration on page 14 Communicator Add-in integration on page 14 Web Browser Add-in application The Avaya ACE Web Browser Add-in provides Microsoft Internet Explorer users the ability to initiate a call directly from any given web page that contains valid telephone numbers. The application searches through the web page and marks any valid numbers. When a user rolls the cursor over the marked element, a button appears that can be clicked to initiate a call from the user s preferred device. Office Add-in application The Avaya ACE Office Add-in communication enables the Microsoft Office 2007 and Microsoft Office 2010 suites. Office Add-in provides Outlook 2007 and Outlook 2010 users the ability to select any Outlook item (mail, contact, calendar, task, journal items), email address, or telephone number, and initiate a call with a simple click. The Office Add-in also provides a Web Browser and Office Add-ins Application Fundamentals March 2011 13

Overview Smart Tag that recognizes telephone numbers within Word documents, Excel Spreadsheets, Power Point presentations, and within the body of an email displayed in Outlook. Hot Desking integration As part of the Web Browser and Office Add-in applications, you can integrate with the Avaya ACE Hot Desking application. The Hot Desking application provides a portal that allows users to manage their various phone and video devices. Through the hot desking interface, users can see their provisioned devices and select a new primary device. Users can also register a phone as a hot desk phone, reroute calls to alternative mobile and voice mail devices, control call forwarding of a desk phone (if call forwarding is supported), and search for contacts within a corporate directory. The Web Browser and Office Add-in applications cannot integrate with the Hot Desking application if they are integrating with the Avaya ACE Communicator Add-in. Communicator Add-in integration The Avaya ACE Web Browser Add-in and the Avaya ACE Office Add-in applications can integrate with the Avaya ACE Communicator Add-in to provide a unified user experience across all Avaya ACE desktop applications. The following describes the changes in the user experience when you integrate the add-ins with the Communicator Add-in: The Call Assistant found in the Browser and Office Add-ins does not provide the call status information to the user. Instead, when the user initiates a call using either the Browser or Office Add-in, the user is presented with a Communicator conversation window indicating the correct call status of the call. The Browser and Office Add-ins do not provide an interface for selecting the primary device when running in Communicator mode. The user's primary device must be set to the device that was created for the Communicator add-in, namely the work number provisioned against the Office Communications Server (OCS) user. For full functionality, the user must be logged into the Microsoft Communicator Client and must have installed and activated the Communicator Add-in. For more information on the Avaya ACE Communicator Add-in, see Avaya Agile Communication Environment Administration Microsoft Office Communications Server Integration (NN10850 012). 14 Web Browser and Office Add-ins Application Fundamentals March 2011

Authorization application Authorization application The Authorization application registers the Web Browser and Office Add-in applications into the AIE authorization database and registers the permissions the add-in applications want to have authorized by the database. The Authorization application restricts users from accessing and using the add-in applications unless they have the proper permissions. The Authorization application uses roles to group the permissions a user needs to access and use an add-in application. The Avaya ACE that is communicating with the AIE hosting the add-in applications must include a user group called Avaya Authorization Roles to which the system adds the authorization user groups. This group has a parent user group of SystemAdminGroup and a user group type of System Administrator. Through the AIE GUI, you add the role DCE (Desktop Communication Enablement) to the Authorization application. This creates the authorization_dce user group on ACE. The user that is running the Configurator must be a member of the authorization_dce user group on ACE. When the Configurator builds the install packages for the Web Browser and Office Add-in applications, it creates an Authorization application on the AIE called DCE and the following permissions: DCE_BrowserAddin DCE_OfficeAddin You must add the BrowserAddinUser and OfficeAddinUser roles to the DCE authorization application on AIE. This creates the DCE_BrowserAddinUser and DCE_OfficeAddinUser user groups on ACE. Once you add the appropriate permissions to these roles, you can assign the end-users of the Web Browser and Office Add-in applications to the appropriate user group on ACE. Configurator The Avaya ACE Configurator is an administrative tool used to configure and build the Web Browser and Office Add-in application install packages with the needed AIE configuration details and any specific application configuration prior to distribution to end users. The Configurator installation package is available on the Avaya ACE Applications disk in the Desktop Communications Enablement (DCE) folder. Administrators must have Microsoft.NET Framework 3.5 to run the Configurator installation package. For a complete list of system requirements, see Configurator requirements on page 20. Web Browser and Office Add-ins Application Fundamentals March 2011 15

Overview The Configurator produces a configured install package containing the Web Browser Add-in or the Office Add-in or both. You can distribute these install packages to end users. For more information on the install packages, see the following: Web Browser Add-in install package on page 16 Office Add-in install package on page 17 Important: You can use the Configurator to build the install package for the Avaya ACE Communicator Add-in. You can include this install package with the builds of the Web Browser and Office Add-in install packages. For more information on the Avaya ACE Communicator Add-in solution and requirements, including using the Configurator to build the install package, see Avaya Agile Communication Environment Administration Microsoft Office Communications Server Integration (NN10850 012). Web Browser Add-in install package Following the successful build of the Web Browser Add-in, the Web Browser Add-in directory contains two packages generated for the Web Browser Add-in: a 32-bit install package found in the x86 folder and a 64-bit install package found in the x64 folder. The 32-bit install package contains the following: vs90_piaredist WindowsInstaller3_1 DCE.BrowserAddin.reg DCE.BrowserAddin.Wow6432Node.reg DCE.BrowserAddin.x86.msi setup.exe The 64-bit install package contains the following: vs90_piaredist WindowsInstaller3_1 DCE.BrowserAddin.reg DCE.BrowserAddin.x64.msi setup.exe To support hot desking, users running a 64 bit operating system must install the 32 bit Web Browser Add-in install package as Adobe Flash does not support 64 bit. Users can run the MSI file to install the Web Browser Add-in. This is successful if all of the prerequisite software exists. Otherwise, the installer prompts the user to run the setup.exe file to install the prerequisite software before installing the Web Browser Add-in. 16 Web Browser and Office Add-ins Application Fundamentals March 2011

Configurator Users must have Microsoft.NET Framework 3.5 which is not packaged with the Web Browser Add-in. If the installer detects that a user is missing Microsoft.NET Framework 3.5, the installer provides the url to download the needed software. Users must have administrative privileges to install the software on their systems. The DCE.BrowserAddin.reg file is a registry file that contains only the configuration information related to the Web Browser Add-in. Provide this file to users who have already installed the Web Browser Add-in and only require an update of the configuration data. Users must have administrator privileges to install the configuration update and must run the following command: regedit.exe /s DCE.BrowserAddin.reg The DCE.BrowserAddin.Wow6432Node.reg file is a registry file that only contains the configuration information related to the Web Browser Add-in. Provide this file to users who need to update x86 installations on x64 platforms. Users must have administrator privileges to install the update and must run the following command: regedit.exe /s DCE.BrowserAddin.Wow6432.reg Office Add-in install package Following the successful build of the Office Add-in, the Office Add-in directory contains the following: two packages generated for the Office 2010 Add-in: a 32-bit install package found in the x86 folder and a 64-bit install package found in the x64 folder one package generated for the Office 2007 Add-in: a 32-bit install package found in the x86 folder The 32-bit install packages contains the following: VSTOR30 WindowsInstaller3_1 Office2007PIA (for Office 2007 package only) DCE.OfficeAddin.reg DCE.OfficeAddin.Wow6432Node.reg DCE.OfficeAddin.x86.msi setup.exe The 64-bit install package contains the following: VSTOR30 WindowsInstaller3_1 DCE.OfficeAddin.reg Web Browser and Office Add-ins Application Fundamentals March 2011 17

Overview DCE.OfficeAddin.x64.msi setup.exe Users can run the MSI file to install the Office Add-in. This is successful if all of the prerequisite software exists. Otherwise, the installer prompts the user to run the setup.exe file to install the prerequisite software before installing the Office Add-in. Users must have Microsoft.NET Framework 3.5 which is not packaged with the Office Addin. If the installer detects that a user is missing Microsoft.NET Framework 3.5, the installer provides the url to download the needed software. Users must have administrative privileges to install the software on their systems. The DCE.OfficeAddin.reg file is a registry file that contains only the configuration information related to the Office Add-in. Provide this file to users who have already installed the Office Addin and only require an update of the configuration data. Users must have administrator privileges to install the configuration update and must run the following command: regedit.exe /s DCE.OfficeAddin.reg The DCE.OfficeAddin.Wow6432Node.reg file is a registry file that only contains the configuration information related to the Office Add-in. Provide this file to users who need to update x86 installations on x64 platforms. Users must have administrator privileges to install the update and must run the following command: regedit.exe /s DCE.OfficeAddin.Wow6432.reg 18 Web Browser and Office Add-ins Application Fundamentals March 2011

Chapter 4: System requirements Review the system requirements before building the install packages for the Avaya Agile Communication Environment (ACE) Web Browser and Office Add-in applications and deploying the install packages to end users. Navigation Avaya ACE requirements on page 19 AIE requirements on page 19 Configurator requirements on page 20 Web Browser Add-in requirements on page 20 Office Add-in requirements on page 21 Service provider requirements on page 22 Web services requirements on page 22 Avaya ACE requirements Make sure the following Avaya ACE requirements are met before you build the install packages for the Web Browser and Office Add-in applications. The Avaya ACE server must be installed and functional. See Avaya Agile Communication Environment Planning and Installation (NN10850-004). You must have administrator privileges on the Avaya ACE server. You must be familiar with Avaya ACE user management. For more information, see Avaya Agile Communication Environment Administration (NN10850-005). AIE requirements Make sure the following Avaya ACE AIE requirements are met before you build the install packages for the Web Browser and Office Add-in applications. Avaya ACE Application Integration Engine (AIE) installation, configuration, and integration with Avaya ACE is complete. For more information, see Avaya Agile Web Browser and Office Add-ins Application Fundamentals March 2011 19

System requirements Communication Environment Application Integration Engine Fundamentals (NN10850-021). The AIE must be deployed in Active Directory mode (with Integrated Windows Authentication). Configurator requirements The Configurator is an administrative tool used to configure and build the install packages for the Avaya ACE Web Browser and Office Add-in applications with the needed Avaya AIE configuration details and any specific application configuration prior to distribution of the addins to end users. See Table 1: Configurator requirements for administrators on page 20 for the administrator's requirements for installing the Configurator. Table 1: Configurator requirements for administrators Software prerequisites Supported OS Privileges Administrators must have the following software installed on their systems before installing the Configurator: Microsoft.NET Framework 3.5 Administrators must be running one of the following operating systems (OS): Microsoft Windows XP SP3 Microsoft Windows Vista SP1 Microsoft Windows 7 (including 64- bit versions) Make sure the OS is fully updated with all Microsoft patches. Administrator Web Browser Add-in requirements See Table 2: Web Browser Add-in requirements for end users on page 21 for the end user requirements for installing and using the Web Browser Add-in. Users should close all existing IE browser sessions before they install the Web Browser Addin. 20 Web Browser and Office Add-ins Application Fundamentals March 2011

Office Add-in requirements Table 2: Web Browser Add-in requirements for end users Software prerequisites Supported OS Supported browsers Privileges Users must have the following software installed on their systems before running the Browser Add-in installer. Microsoft.NET Framework 3.5 Avaya ACE Communicator Add-in (if integrating with the Communicator Add-in) Adobe Flash Player 9 (if integrating with Hot Desking) Users must be running one of the following operating systems (OS): Microsoft Windows XP SP3 Microsoft Windows Vista SP1 Microsoft Windows 7 (including 64-bit versions) Make sure the OS is fully updated with all Microsoft patches. Users must be using one of the following browsers: Internet Explorer 6 Internet Explorer 7 Internet Explorer 8 Administrator Office Add-in requirements See Table 3: Office Add-in requirements for end users on page 21 for the end user requirements for installing and using the Office Add-in. Users should close all existing Outlook sessions before they install the Office Add-in. Table 3: Office Add-in requirements for end users Software prerequisites Supported OS Privileges Users must have the following software installed on their systems before running the Office Add-in installer: Microsoft.NET Framework 3.5 Adobe Flash Player 9 (if integrating with Hot Desking) Avaya ACE Communicator Add-in (if integrating with the Communicator Add-in) Users must be running one of the following operating systems (OS): Microsoft Windows XP SP3 Microsoft Windows Vista SP1 Microsoft Windows 7 (including 64- bit versions) Make sure the OS is fully updated with all Microsoft patches. Administrator Web Browser and Office Add-ins Application Fundamentals March 2011 21

System requirements Software prerequisites Supported OS Privileges Microsoft Office 2007 and Microsoft Office Suite 2007 Service Pack 2 or Microsoft Office 2010 The installer installs the following software if missing: Microsoft Installer 3.1 Microsoft Office Primary Interop Assembles VSTO 3.0 Runtime Service provider requirements The following service providers support the Web Browser and Office Add-in applications: Avaya Aura TR/87 Avaya Aura SIP Avaya CS 1000 TR/87 Avaya CS 1000 SIP CUCM SIP CUCM JTAPI Communication Server 2100 (CS 2100) TR/87 For more information on the service providers, refer to Avaya Agile Communication Environment Administration (NN10850 005). Web services requirements The Web Browser and Office Add-in applications make use of the following web services: Third Party Call Control (v2) User Profile For more information on the web services, refer to Avaya Agile Communication Environment Web Services (NN10850 007). 22 Web Browser and Office Add-ins Application Fundamentals March 2011

Chapter 5: Building the install packages Build the install packages for the Avaya Agile Communication Environment (ACE) Web Browser and Office Add-in applications. Prerequisites for building the install packages You are familiar with the System requirements on page 19. Building the install packages procedures The following task flows shows you the sequence of procedures you perform to build the install packages for the Web Browser and Office Add-in applications. Web Browser and Office Add-ins Application Fundamentals March 2011 23

Building the install packages Figure 1: Building the install packages procedures 24 Web Browser and Office Add-ins Application Fundamentals March 2011

Configuring the Authorization application Building the install packages navigation Configuring the Authorization application on page 25 Installing the Configurator on page 26 Building the Web Browser Add-in install package on page 27 Building the Office Add-in install package on page 28 Configuring DCE authorization on page 29 Adding users to the Web Browser Add-in user group on page 30 Adding users to the Office Add-in user group on page 31 Configuring the Authorization application Prerequisites You have administrator privileges on the Avaya ACE server. The AIE software was installed in Active Directory mode. You know the host name or IP address of the Avaya ACE host that is communicating with the AIE hosting the add-in applications. You know the host name or IP address and port of the AIE server that is hosting the addin applications. Before building the install packages for the add-in applications, configure the Authorization service for use with the Web Browser and Office Add-in applications. 1. Open a web browser and log in to the Avaya ACE GUI as administrator. https://<avaya_ace_host_ip>:9443/oamp 2. On the menu bar, choose Security, User Group Management, and then Create User Group. 3. In the Create User Group window, enter the following name for the user group. Make sure the name reflects the capitalization and spaces as shown. Avaya Authorization Roles 4. In the User Group Type field, select System Administrator from the drop-down menu. 5. In the Parent User Group field, select SystemAdminGroup from the drop-down menu. 6. In the Membership Information dialog box, move the AIE system user from the Available Users list to the User Group Members list. Web Browser and Office Add-ins Application Fundamentals March 2011 25

Building the install packages 7. Click Submit to save your changes. 8. Open a web browser and log in to the AIE GUI. 9. On the menu bar, choose Applications, Authorization, and then Add Role to Application. 10. From the Registered applications drop-down list, select authorization. 11. In the Name of role to add field, enter DCE and click Add. The authorization_dce role appears in the Roles assigned to application list. The Authorization application creates the authorization_dce user group on the Avaya ACE server that is communicating with this AIE. 12. On the menu bar, choose Applications, Authorization, and then Add Permission to Role. 13. From the Registered applications drop-down list, select authorization. 14. From the Roles assigned to application list drop-down list, select authorization_dce. 15. From the Select permission to add drop-down list, select authorization_apipermission and click Add. 16. From the ACE GUI, add the user who will be using the Configurator to create the add-in install packages as a member of the authorization_dce user group. Installing the Configurator Prerequisites You are a member of the authorization_dce user group on Avaya ACE. You are running one of the following operating systems: - Microsoft Windows XP (patched to a minimum of SP2) - Microsoft Windows Vista - Microsoft Windows 7 You have Microsoft.NET Framework 3.5 SP1. You have the DCE.configurator.msi file on your desktop. Install the Avaya ACE Configurator. The Configurator is an administrative tool used to configure and build the install packages for the Avaya ACE Web Browser and Office Add-in applications with the needed Avaya ACE AIE configuration details and any specific application configuration prior to distribution of the add-ins to end users. 26 Web Browser and Office Add-ins Application Fundamentals March 2011

Building the Web Browser Add-in install package 1. Double-click the DCE.Configurator.msi file to launch the Windows installer for the Avaya ACE Configurator. 2. When the Avaya ACE Configurator installer opens, click Next. 3. When the Avaya ACE Configurator setup wizard opens, click Next. 4. In the License Agreement window, click I Agree to accept the license agreement. 5. In the Select Installation Folder window, specify a path to the installation folder for the Avaya ACE Configurator and click Next. 6. In the Confirm Installation window, click Next to start the installation. 7. In the Installation Complete window, click Close to exit the setup wizard. A dialog prompts you to view the documentation associated with the Avaya ACE Configurator. 8. To view the Avaya ACE Configurator documentation, click Yes. Otherwise, click No. The Avaya ACE Configurator icon appears on your desktop. Building the Web Browser Add-in install package Prerequisites You have installed the Avaya ACE Configurator. You know the host URL for the Avaya ACE AIE server that is hosting the Web Browser Add-in application. Build the install package for the Avaya ACE Web Browser Add-in to allow users to install the Web Browser Add-in application. 1. Double-click the Avaya ACE Configurator icon to open the Avaya ACE Configurator tool. 2. On the AIE tab, enter the Host URL of the Avaya AIE server that is hosting the addin application. 3. In the Destination Folder, enter the folder where the installation package will be built or click the folder icon to browse for a destination folder. 4. Select the Integration tab. 5. On the Application window, enable the radio button for one of the following options: Web Browser and Office Add-ins Application Fundamentals March 2011 27

Building the install packages None if there is no integration Hot Desking if the add-in application will integrate with the Hot Desking application Communicator Add-in if the add-in application will integrate with the Communicator Add-in 6. Select the Browser Add-in tab. 7. On the Browser Add-in Configuration window, enable the Build check box to build an install package for the Web Browser Add-in. 8. Create custom number matching rules as required to be included in the Web Browser Add-in install package. Refer to the Configurator online help for more information on creating custom number matching rules. 9. Click the arrow button at the bottom of the Configurator interface to build the install package for the Web Browser Add-in. The Configurator validates the information that you entered. If the information is valid, the Configurator creates the add-in installation files that contain all of the validated AIE configuration and application custom configuration. If the build is successful, the Avaya ACE Applications folder opens displaying the Browser Add-in folder. Building the Office Add-in install package Prerequisites You have installed the Avaya ACE Configurator. You know the host URL for the Avaya ACE AIE server that is hosting the Office Add-in application. Build the install package for the Avaya ACE Office Add-in to allow users to install the Office Add-in application. 1. Double-click the Avaya ACE Configurator icon to open the Avaya ACE Configurator tool. 2. On the AIE tab, enter the Host URL of the Avaya AIE server that is hosting the addin application. 3. In the Destination Folder, enter the folder where the installation package will be built or click the folder icon to browse for a destination folder. 28 Web Browser and Office Add-ins Application Fundamentals March 2011

Configuring DCE authorization 4. Select the Integration tab. 5. On the Application window, enable the radio button for one of the following options: None if there is no integration Hot Desking if the add-in application will integrate with the Hot Desking application Communicator Add-in if the add-in application will integrate with the Communicator Add-in 6. Select the Office Add-in tab. 7. On the Office Add-in Configuration window, enable the Build check box to build an install package for the Office Add-in. 8. Create custom number matching rules as required to be included in the Office Addin install package. Refer to the Configurator online help for more information on creating custom number matching rules. 9. Click the arrow button at the bottom of the Configurator interface to build the install package for the Office Add-in. The Configurator validates the information that you entered. If the information is valid, the Configurator creates the add-in installation files that contain all of the validated AIE configuration and application custom configuration. If the build is successful, the Avaya ACE Applications folder opens displaying the Office Add-in folder. Configuring DCE authorization Prerequisites The Authorization application is configured; see Configuring the Authorization application on page 25. A build of the add-in application install packages was performed. An AIE GUI session is open. Add the BrowserAddinUser and OfficeAddinUser roles to the DCE authorization application and assign the permissions. Important: When you add these roles to the DCE authorization application, the system creates the BrowserAddinUser and OfficeAddinUser user groups on the Avaya ACE server that is Web Browser and Office Add-ins Application Fundamentals March 2011 29

Building the install packages communicating with this AIE. ACE users must be members of the corresponding group or groups before they can use the Web Browser or Office Add-in applications. 1. From the menu bar, choose Applications, Authorization, and then Add Role to Application. 2. From the Registered applications drop-down list, select DCE. 3. In the Name of role to add field, enter BrowserAddinUser and click Add. The BrowserAddinUser role appears in the Roles assigned to application list. The Authorization application creates the BrowserAddinUser user group on the Avaya ACE server that is communicating with this AIE. 4. In the Name of role to add field, enter OfficeAddinUser and click Add. The OfficeAddinUser role appears in the Roles assigned to application list. The Authorization application creates the OfficeAddinUser user group on the Avaya ACE server that is communicating with this AIE. 5. On the menu bar, choose Applications, Authorization, and then Add Permission to Role. 6. From the Registered applications drop-down list, select DCE. 7. From the Roles assigned to application list drop-down list, select BrowserAddinUser. 8. From the Select permission to add drop-down list, select DCE_BrowserAddin and click Add. 9. From the Roles assigned to application list drop-down list, select OfficeAddinUser. 10. From the Select permission to add drop-down list, select DCE_OfficeAddin and click Add. Adding users to the Web Browser Add-in user group Prerequisites DCE authorization configuration on the AIE is complete; see Configuring DCE authorization on page 29. Users of the Web Browser Add-in have a corresponding Avaya ACE user ID that matches their Windows account username and includes a telephone contact type. 30 Web Browser and Office Add-ins Application Fundamentals March 2011

Adding users to the Office Add-in user group You have administrator privileges on the Avaya ACE server. You know the IP address of the Avaya ACE server that is communicating with the AIE server hosting the add-in application. Add users as members of the BrowserAddinUser user group on Avaya ACE so they can use the Web Browser Add-in application. 1. Open a web browser and log in to the Avaya ACE GUI as administrator. https://<avaya_ace_host_ip>:9443/oamp 2. On the menu bar, choose Security, User Group Management, and then List/Edit User Groups. 3. On the List User Groups window, click Submit to search by all user groups. 4. From the list of user groups, select the BrowserAddinUser user group. 5. From the Available Users list, move the Web Browser Add-in users to the User Group Members of the BrowserAddinUser group. 6. When you have added all the appropriate users as members of the BrowserAddinUser group, click Submit. Adding users to the Office Add-in user group Prerequisites DCE authorization configuration on the AIE is complete; see Configuring DCE authorization on page 29. Users of the Web Browser Add-in have a corresponding Avaya ACE user ID that matches their Windows account username and includes a telephone contact type. You have administrator privileges on the Avaya ACE server. You know the IP address of the Avaya ACE server that is communicating with the AIE server hosting the add-in application. Add users as members of the OfficeAddinUser user group on Avaya ACE so they can use the Office Add-in application. 1. Open a web browser and log in to the Avaya ACE GUI as administrator. Web Browser and Office Add-ins Application Fundamentals March 2011 31

Building the install packages https://<avaya_ace_host_ip>:9443/oamp 2. On the menu bar, choose Security, User Group Management, and then List/Edit User Groups. 3. On the List User Groups window, click Submit to search by all user groups. 4. From the list of user groups, select the OfficeAddinUser user group. The User Group Details window for the OfficeAddinUser group appears. 5. From the Available Users list, move the Office Add-in users to the User Group Members of the OfficeAddinUser group. 6. When you have added all the appropriate users as members of the OfficeAddinUser group, click Submit. 32 Web Browser and Office Add-ins Application Fundamentals March 2011