DeviceAnywhere Enterprise. Private System Installation Guide. Release 6.0

Transcription

1 Private System Installation Guide Release 6.0

2 Installation Guide 6.0 June 2013 Copyright Notice Copyright Keynote Systems, Inc. All rights reserved THE INFORMATION CONTAINED IN THIS DOCUMENT IS PROVIDED AS IS WITHOUT ANY EXPRESS REPRESENTATIONS OF WARRANTIES. IN ADDITION, KEYNOTE DISCLAIMS ALL IMPLIED REPRESENTATIONS AND WARRANTIES, INCLUDING ANY WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT OF THIRD PARTY INTELLECTURAL PROPERTY RIGHTS. All text and figures included in this publication are the exclusive property of Keynote and may not be copied, reproduced, or used in any way without the express permission in writing of Keynote. Information in this document is subject to change without notice and does not represent a commitment on the part of Keynote. Keynote may have patents or pending patent applications covering subject matter in this document. The furnishing of this document does not give you any license to these patents except as expressly provided in any written license agreement from Keynote. The trademarks or registered trademarks of Keynote Systems, Inc. in the United States and other countries include Keynote, DataPulse, CustomerScope, Keynote Customer Experience Rankings, Perspective, Keynote Red Alert, Keynote WebEffective, The Internet Performance Authority, MyKeynote, SIGOS, SITE, keynote The Mobile & Internet Performance Authority, Keynote FlexUse, Keynote DeviceAnywhere, DeviceAnywhere, Keynote DemoAnywhere, Keynote MonitorAnywhere. All related trademarks, trade names, logos, characters, design and trade dress are trademarks or registered trademarks of Keynote Systems, Inc. in the United States and other countries and may not be used without written permission. All other trademarks are the property of their respective owners. Please forward any comments or suggestions regarding this document to Keynote Support. Keynote Systems, Inc. 777 Mariners Island Blvd. San Mateo, CA ii Keynote Confidential

3 Installation Guide Contents About This Document... 5 Document Outline... 5 Typographical Conventions... 6 Contacting Support... 6 Additional Documentation Introduction Components General Installation Guidelines Infrastructure Requirements System Size and Topology Overview System Requirements Mobile Device Requirements Hardware-Integrated Devices Local Software Devices Rack Space Requirements Power Operating Conditions Database Backup Requirements High Availability Requirements Network and Port Requirements Network Configuration and Tests Connectivity Requirements Anti-Virus Settings Test Procedures Opening a Telnet Session to Test the Connection Server Connectivity Tests Component Installation Database Pre-requisites for Installation Creating and Restoring a Database in SQL Server Configuring the Database DOM Server Installing the DOM Server Verifying DOM Server Installation Access Server Keynote Confidential iii

4 Installation Guide Connectivity Requirements Installing the Access Server Verifying Access Server Installation IIS Web Server Installing and Configuring IIS Verifying IIS Server Installation Portal Connectivity Requirements Installing the DeviceAnywhere Portal License File LiveTest or LiveMonitor Server Connectivity Requirements Installing LiveTest Server Verifying LiveTest Server Installation Ensemble Server Ensemble Server Guidelines Ensemble Server Installation Verifying Ensemble Server Installation DeviceAnywhere Studio Connectivity Requirements Installing DeviceAnywhere Studio on Windows Installing DeviceAnywhere Studio on Mac OS X Mobile Devices Provisioning Packages with Devices Assigning Packages to User Groups Verifying Device Installation System Verification Restarting the Access Server Verifying DeviceAnywhere Functionality iv Keynote Confidential

5 Installation Guide About This Document This Installation Guide outlines the requirements and procedures for installing a test or monitoring environment. With, you can interact with and control real, live devices in order to automate the testing of your mobile application, service, or device. You can also monitor crucial QoS metrics and create reports and analyze trends. If you are upgrading your installation, please contact your Keynote Solutions Consultant for procedures on how to back up your database, upgrade the database schema, deinstall existing software components, and install new components for a successful upgrade. Document Outline In this document: Introduction lists the components of a installation and the order in which they are installed. Infrastructure Requirements describes the configuration of different sized installations. It also lists system requirements, rack space needed, network ports used, mobile device requirements, and power and operating conditions. Network Configuration and Tests describes connectivity requirements and procedures to test connectivity among components. Component Installation contains step-by-step instructions for installing and verifying: SQL Database DeviceAnywhere DOM Server Access Server to control all DeviceAnywhere components IIS Web Server Portal and the default customer License File LiveTest Server or LiveMonitor Server Ensemble Server for communicating with devices DeviceAnywhere Studio client software Mobile Devices (adding to the database) System Verification contains tests and procedures to verify your test environment. Keynote Confidential 5

6 Installation Guide Typographical Conventions The table below describes the typographical conventions used in DeviceAnywhere documentation. Style Element Examples Blue Links and addresses The Document Outline section on this page describes the structure of this manual. Bold User interface elements such as menu items Click My Devices in DeviceAnywhere Studio. Monospace Commands, code output, filenames, directories Right-click the project s test cases directory. Monospace bold User input In a command window, type adb devices. Italic Document titles and emphasis Refer to the Automation User Guide to learn how to script. Contacting Support If you have any comments or suggestions regarding this document, contact Keynote Support. For inquiries about DeviceAnywhere product demonstrations and consulting services, contact your Keynote Solutions Consultant. Customers can find additional support information at or KEY-SYST ( ). Additional Documentation You can find additional documentation on test automation at Enterprise test automation customers with private devices can find additional documentation at Monitoring customers can find information at You can access the documentation web page for your environment from the Help menu in DeviceAnywhere Studio. 6 Keynote Confidential

7 Installation Guide 1 Introduction This chapter lists the components required for installing a system. This chapter also discusses installation guidelines and the order in which to install components. (Componentspecific guidelines and instructions can be found in Component Installation.) 1.1 Components You must install the following components contained provided by Keynote in order to deploy a environment: database (You must also acquire a license for and install SQL Server 2008 or higher) Manages information on users, devices, device usage, test assets, etc. DOM Server to enable HTML5 Web testing (DeviceAnywhereWebTest.exe) you can also use Keynote s DOM Server; please contact your Solutions Consultant for details. Access Server (AccessServer.exe for 32-bit systems, AccessServer64.exe for 64-bit systems) The core component and controller of the environment Portal Web portal for managing user accounts and test results EnterprisePortal_MA.exe for Automation EnterprisePortal_TA.exe for Monitoring license XML file with licenses for the modules you wish to use LiveMonitor Server for automated execution of monitor scripts (LiveMonitor.exe for 32-bit systems, LiveMonitor64.exe for 64-bit systems) LiveTest Server for automated test execution (LiveTest.exe for 32-bit systems, LiveTest64.exe for 64-bit systems) Ensemble Server Server that communicates with mobile devices (EnsembleServer.exe) DeviceAnywhere Studio client software (DeviceAnywhereStudioEnt.exe or DeviceAnywhere Studio.dmg) Client interface for interacting with devices and creating and running test scripts Device profile XML files, procured from Keynote (generally one for each device to be added to the system) NOTE Onboarding of software-integrated and hybrid mobile devices is covered in the platformspecific onboarding guides available at NOTE Components of a environment require a network connection to communicate with each other. The following components are automatically installed with the Portal:.NET 4 runtime framework Microsoft ASP.NET AJAX Extension (ASP AJAX 1.0) Keynote Confidential 7

8 Installation Guide Microsoft WSE 3.0 In addition, you must install: SQL Server 2008 or higher (Express, Standard, or Enterprise) on the machine hosting the database For specific information on SQL Server installation, refer to Microsoft SQL Server documentation. IIS Server v6 or 7 on the machine hosting the Portal JDK 1.5+ if installing DeviceAnywhere Studio on Macintosh machines 1.2 General Installation Guidelines Start Here before attempting to install a environment, please review Infrastructure Requirements in detail. In particular, review the system size and topology options and system requirements so you can determine your hardware needs. Your Keynote Solutions Consultant can assist you with designing your deployment configuration. Order of Component Installation Please install components in the order listed below. You must start with installing SQL Server and loading the database before continuing with the standard installation process. components are installed in this order: 1 SQL Server 2008 and database 2 DOM Server (if not using Keynote s DOM Server) 3 Access Server 4 Portal (you should already have installed the IIS Server) 5 License file 6 LiveMonitor or LiveTest Server 7 Ensemble Server 8 DeviceAnywhere Studio 9 Devices (adding to database) The remainder of this document will walk you through the installation process, starting with configuring your deployment, testing your network configuration, and then installing each of the above components in turn. Finally, this document will cover how to verify that your installation is successful. 8 Keynote Confidential

9 Installation Guide 2 Infrastructure Requirements This section provides guidelines for purchasing hardware, allocating rack space, estimating network and power requirements, and setting up the data center for your environment. When you have finished reviewing this section, you should be able to set up and connect the hardware components of your installation. 2.1 System Size and Topology Keynote supports deploying components in a single location or distributed over more than one location. In a distributed system, core components are housed in the same physical location while the Ensemble Servers and attached devices may be deployed across remote locations. Table 2-1 provides a description of small, medium, and large deployments and outlines the recommended hardware to support installation. In general, we recommend up to 4 smartphones or 2 tablets attached to a single Ensemble Server. Table 2-1 Deployment Sizes Size Small Description A small deployment contains from 2 4 devices attached to an Ensemble Server. Computer 1 = SQL Server and database, Access Server, Portal Computer 2 = LiveTest or LiveMonitor Server + DOM Server (separate server for each component recommended) Computer 3 = Ensemble Server (less than 4 devices) NOTE If your tests run often and collect a lot of proofs (screenshots/video), we recommend using a separate machine as the database server. Medium/Large A medium deployment supports a total of 1 8 devices (with no more than 4 smartphones or 2 tablets per Ensemble Server). A large deployment supports more than 8 devices (with no more than 4 smartphones or 2 tablets per Ensemble Server). Components of medium or large deployments are installed separately. The total number of computers you need will depend on the number of devices that can be attached to each Ensemble Server for best performance. Computer 1 = SQL Server and database Computer 2 = DOM Server Computer 3 = Access Server, Portal Computer 3 = LiveTest or LiveMonitor Server Computer 5 = Ensemble Server for 1 4 devices Computer 6 = Ensemble Server for 1 4 devices Add Ensemble Servers as required. NOTE If you have any questions about installation or designing your deployment, e.g., how many devices to attach to an Ensemble Server, contact your Keynote Solutions Consultant. Keynote Confidential 9

10 Installation Guide 2.2 Overview Depending on the number of devices and locations in your installation, your hardware requirements will vary. When planning your deployment, consider the following: System size and topology System requirements Ensemble Server guidelines Mobile device requirements (mobile devices attached to the Ensemble Server) Rack space requirements Network and port requirements Power and operating conditions Database backup requirements High availability requirements 2.3 System Requirements Minimum hardware requirements and operating systems tested for components are: Table 2-2 Minimum System Requirements for Individual Components DA Component Hardware/Software Requirement Notes Database Server Processor speed Core i5 for DeviceAnywhere Enterprise Automation Quad core (e.g., Xeon) for Monitoring DeviceAnywhere DOM Server Memory 4 GB RAM for automation 8 GB for monitoring (16 GB recommended) Hard drive space Database 250 GB (as needed) Microsoft SQL Server 2008 or higher (Express, Standard, or Enterprise Editions) Operating system Windows Server 2003 Windows 7 Windows Server 2008 x86 and x64 supported on Windows. You cannot avail of more than 4 GB RAM on x86 machines. Processor speed Core i5 Installing this yourself Memory 4 GB RAM is optional; you can use Keynote s DOM Hard drive space 40 GB Server instead Operating system Windows Server 2003 contact your Solutions Windows 7 Consultant. 10 Keynote Confidential

11 Installation Guide DA Component Hardware/Software Requirement Notes Windows Server 2008 Only 64-bit processing supported. Access Server Processor speed Core i5 for automation DeviceAnywhere Enterprise Portal LiveTest or LiveMonitor Server Memory Hard drive space Core i7 for monitoring 4 GB RAM (8 GB recommended) 20 GB Operating system Windows Server 2003 Windows 7 Windows Server 2008 x86 and x64 supported on Windows. You cannot avail of more than 4 GB RAM on x86 machines. 50 concurrent users Processor speed Core i3 100 concurrent users Memory 4 GB RAM supported (only 10 on Windows XP) Hard drive space 10 GB Operating system Windows Server 2003 Windows 7 Windows Server 2008 x86 and x64 supported on Windows. You cannot avail of more than 4 GB RAM on x86 machines. Client-side browser Google Chrome Internet Explorer Firefox Safari Additional software IIS Server v6 or 7.NET 4.0 runtime framework, ASP AJAX 1.0, and WSE 3.0 are provided by Keynote. Processor speed Memory Hard drive space Core i5 4 GB RAM 200 GB Operating system Windows Server 2003 Windows Server bit processing is required because of memory requirements. Ensemble Server Processor speed Core i3 Maximum of 2 4 Memory 3 or 4 GB RAM concurrently attached devices Hard drive space 10 GB supported. Operating system Windows XP Install this Windows Server 2003 component on a Windows 7 separate machine from other server Windows Server 2008 components for Ensemble Server is compatible with optimum Windows 7 x64. Only x86 supported on performance. other Windows systems. You cannot avail of more than 4 GB RAM on x86 machines. Keynote Confidential 11

12 Installation Guide DA Component Hardware/Software Requirement Notes USB ports USB 2.0 ports (3.0 recommended) Add-in USB cards to create 4-6 ports Directly attached smart devices require up to 1 port; hardware-integrated devices require up to 2. DeviceAnywhere Studio Processor speed 2 GHz dual core (Pentium 4 or higher) Memory Hard drive space 2 GB RAM 10 GB Operating system Windows Vista Windows 7 Windows Server 2008 x86 and x64 supported on Windows. Mac OS 10.2 and higher Linux is only supported for manual testing JDK v1.7 or higher must be installed for Mac. Screen resolution 1600 x 900 or higher Optional: DeviceAnywhere Addin for UFT Additional Optional audio card for sound input/output JDK v1.7+ for Mac Operating system Windows 2003 Windows Server 2008 Windows 7 Windows 7 x64 is recommended. Required software HP UFT v11.0 or 11.5 DeviceAnywhere Studio For complete requirements, refer to DeviceAnywhere Enterprise for UFT Installation and User Guide. NOTES Components of a environment require a network connection to communicate with each other. If you have any questions about installation or designing your deployment, contact your Keynote Solutions Consultant. 2.4 Mobile Device Requirements Mobile devices are attached or onboarded to Ensemble Servers. The requirements for devices vary depending on the type of device control methodology employed Hardware-Integrated Devices The Direct-to-Device Hardware methodology is used to control hardware-integrated devices. Device input/output controls are hardwired to a casing, which is attached to an Ensemble Server. Hardware-integrated devices require the following: Power outlet for hardware-integrated device casing USB 2.0 (3.0 recommended) port on Ensemble Server for connection to hardware-integrated device case 12 Keynote Confidential

13 Installation Guide Optional: Second USB 2.0 port (3.0 recommended) on Ensemble Server for data cable to hardwareintegrated device NOTE Keynote provides the power supply for the device casing: 6V 3A (12W). ipad devices have a 12V power supply. Keynote provides the required USB cables Local Software Devices The Direct-to-Device Software methodology is used to control local software devices. Devices are connected to the Ensemble Server via USB cable or wirelessly, via Wi-Fi or Bluetooth. Local software devices require the following: Some software-integrated devices require one available USB 2.0 port on the Ensemble Server check the appropriate platform-specific onboarding guide at Platform-specific software prerequisites for onboarding devices are detailed in the onboarding guides. 2.5 Rack Space Requirements After sizing your installation, you should consider the rack space required. Racks can be filled either front only or front and back. Figure 2-1 shows the front and side view of a rack. Our recommended rack equipment can be found at The rack units needed for each component is given in the table below. Table 2-3 Rack Space Requirements Server/Client Computers SQL Server and database Access Server, DeviceAnywhere Enterprise Portal Ensemble Server Device (hardware integrated) PDU Description 2U rack mountable-server 2U rack mountable-server 1U or 2U rack-mountable server (must support USB cards) 2U or 5U (for tablet devices) NOTE Device casings only take up the front of the rack space; for every 2U of rack space, you can install one case in the front and one in the back. 1U Once the rack has been constructed, insert the servers according to Figure 2-1. In general, the core servers should be placed at the bottom of the rack. An example data center rack layout supporting 24 mobile devices is illustrated in Figure 2-2. NOTE DeviceAnywhere recommends rack-mounting hardware-integrated devices; however, this is not a requirement. In smaller deployments it might be easier to stack devices in a lab area or on a desk. Keynote Confidential 13

14 Installation Guide Figure 2-1 Rack Front and Side Views Front View Device 3 Device 3 Side View Device 2 Device 2 Device 4 Device 1 Device 1 PDU Ensemble Server 5 Ensemble 5 Space for cable runs Space for cable runs Device 3 Device 3 Device 5 Device 2 Device 2 Device 4 PDU Device 1 Device 1 Space Ensemble Server 4 Ensemble 4 Device 3 Device 3 Device 5 Device 2 Device 2 Device 4 PDU Device 1 Device 1 Space Ensemble Server 3 Ensemble 3 42 U Device 3 Device 1 (tablet) Device 1 Device 2 PDU Ensemble Server 2 Ensemble 2 Space for cable runs Space for cable runs Device 3 Device 3 Device 5 Device 2 Device 2 Device 4 PDU Device 1 Device 1 Space Ensemble Server 1 Ensemble 1 Access Server DB Server UPS 2U Access DB UPS 19" 27 7/8" 14 Keynote Confidential

15 Installation Guide Figure 2-2 Example Data Center Rack Layout 24 Devices 2.6 Power In general, each rack requires a 20A circuit to power the servers and the devices. Servers require between 1.5A and 3A of power. The power requirement for devices is not significant compared to that of the Windows servers (15 devices = 1A). Plug primary and redundant power cables into separate PDUs but use the same port scheme for simplicity. Keynote Confidential 15

16 Installation Guide 2.7 Operating Conditions Devices should be maintained under the following operating conditions: Operating temperature: 15C 25C Storage temperature: 15C 25C 2.8 Database Backup Requirements Consider procedures to back up the database on a regular basis. The database is the only part of the technology stack that needs to be backed up. All the other components of the system are stateless and can quickly be restored by re-installing the software. It is extremely important to back up the database regularly. 2.9 High Availability Requirements Install an Uninterrupted Power Supply (UPS) in each rack for maximum uptime Network and Port Requirements The DeviceAnywhere software components communicate with each other over TCP/IP. Before you begin installation, make sure that you have configured all the required ports based on the port requirements outlined below. Default port settings are listed here. Table 2-4 Port Requirements DeviceAnywhere Servers Description Open Ports SQL Server 2008 Database Access Server DeviceAnywhere Enterprise Portal Ensemble Server DeviceAnywhere Studio The Access Server and the DeviceAnywhere Portal communicate with the database. The default SQL Server port is All DeviceAnywhere Studio clients and the DeviceAnywhere Portal server must be able to communicate with the Access Server over TCP/IP on port 443. Users are authenticated through the Access Server. The Portal is a web portal for system administration and for viewing test results. It is a Web application running on the standard Web port, 80. The Ensemble Server communicates with mobile devices. Users interacting with devices in DeviceAnywhere Studio communicate on port 443 with the Ensemble Server. This server must therefore accept inbound traffic on port 443. The Ensemble Server must also be able to send outbound communication to the Access Server on port 443. NOTE The Access Server and Ensemble Servers should be installed on different computers. DeviceAnywhere Studio is the client software used to access devices and create test assets. All server components above, with the exception of the Database Server, must be accessible from DeviceAnywhere Studio Reserved for future Web services In Out n/a NOTE The ports used in the DeviceAnywhere are configurable. Consult your Keynote Solutions Consultant for further information on using different ports. 16 Keynote Confidential

17 Installation Guide 3 Network Configuration and Tests Once you have set up the hardware for your installation in one or more data centers based on the size and topology of your system, you should review your port assignments and test communication using Telnet commands. 3.1 Connectivity Requirements The following connectivity requirements are needed for a installation: The Access Server and Portal must be able to connect to the database. DeviceAnywhere Studio users must be able to connect to the Access Server by providing its IP address/machine name appended with the Access Server port (this documented in DeviceAnywhere Studio Installation for Windows). If a user needs to access the test environment over the Internet, then an external IP Address is required. DeviceAnywhere Studio must be able to connect to the Ensemble Server(s) to acquire devices. All other server components such as the Portal and distributed Ensemble Servers must be able to connect to the Access Server by providing its IP address/hostname. 3.2 Anti-Virus Settings Some anti-virus software has port filtering settings turned on for port 443 by default. Since all data communication between DeviceAnywhere Studio and servers occurs on port 443, this can delay response time. Remove port filtering on port 443 to correct the problem. NOTE Kaspersky Anti-virus software has port filtering turned on for port 443 by default. If the Access Server is configured on a port other than 443, remove port filtering on that port. There are some default port assignments that facilitate communication between the DeviceAnywhere Enterprise servers; see Table 2-4 Port Requirements in DeviceAnywhere Infrastructure Requirements. NOTE The ports used in the environment are configurable. Consult your Keynote Solutions Consultant for further information on using non-default ports. 3.3 Test Procedures Before installing software components, execute the tests described in Table 3-1 below. These tests are based on default port settings. If you wish to configure your ports differently, then substitute your port numbers in these tests. Make sure to verify the connection between all the components of your installation Opening a Telnet Session to Test the Connection Use the telnet command in a DOS command prompt window to test your port settings and communication between software components. Start a Telnet session on a Windows machine: Keynote Confidential 17

18 Installation Guide 1 Go to the Start menu and select Run. 2 Type cmd to bring up a DOS command prompt window. 3 Type the telnet command in the window in the format shown: telnet <IP_Address> <Port_Number> Results: When access to the server in question is successful, the DOS window appears blank. When access to the server in question is unsuccessful, you will see an error message. Figure 3-1 below illustrates the error message generated when access to a server fails. In this example, an attempt was made to connect to on port 443. Repeat this procedure to run all the tests listed in Table 3-1 below. Figure 3-1 Telnet Error Message Server Connectivity Tests Table 3-1 Server Connectivity Tests # Action Expected Result 1 Action: Open a Telnet session from one of the client machines to port 443 on the machine that will host the Access Server. Command: telnet <Access_Server_IP> Action: Open a Telnet session from one of the client machines to port 80 on the machine that will host the Portal. Command: telnet <Portal_Server_IP> 80 3 Action: Open a Telnet session from each Ensemble Server machine to Port 443 on the machine that will host the Access Server. Command: telnet <Access_Server_IP> Action: Open a Telnet session from the Access Server to port 1433 on the machine that will host the database server. Command: telnet <DB_Server_IP> Action: Open a Telnet session from the Portal to port 1433 on the machine that will host the database server. Command: telnet <DB_Server_IP> 1433 DOS command prompt window appears blank. DOS command prompt window appears blank. DOS command prompt window appears blank. DOS command prompt window appears blank. DOS command prompt window appears blank. 18 Keynote Confidential

19 Installation Guide 4 Component Installation This section describes the procedures for installing individual components and devices to deploy the test environment. At this point, you should have determined the size of your system, set up your data center, and tested the connectivity between DeviceAnywhere components. This chapter will take you through each of these following steps in order: 1 Creating and restoring a blank database (you need to have installed and configured SQL Server 2008) 2 Installing the DOM Server 3 Installing the Access Server 4 Installing and configuring IIS 5 Installing the Portal 6 Installing the LiveTest or LiveMonitor Server 7 Creating a customer instance 8 Placing the enterprise customer license provided by your Technical Account Manager 9 Installing the DeviceAnywhere Ensemble Server(s) 10 Installing DeviceAnywhere Studio on client machine(s) 11 Adding device information to the database 4.1 Database This section contains the steps required to set up the SQL database Pre-requisites for Installation SQL Server 2008 (or higher) installed and set up to use mixed mode authentication SQL Server Management Studio this is required to create a new database. SQL Server Configuration Manager this is required to make database configuration changes that allow the Access Server and the Portal server to communicate with the database. The database backup file complete_da.bak Creating and Restoring a Database in SQL Server 2008 You must first create a new database and then restore the database. 1 Place the database backup file in an appropriate location on the database server, e.g., C:/DA Databases/<DABackupFile>.bak. Keynote Confidential 19

20 Installation Guide 2 Launch SQL Server 2008 Management Studio (e.g., Start > All Programs > Microsoft SQL Server 2008 R2 > SQL Server Management Studio) and log in. 3 Right-click Databases and choose New Database to create a new database. 20 Keynote Confidential

21 Installation Guide 4 Provide a name for the new database. 5 Click the ellipsis buttons to choose the Path where you want the database MDF and LDF files to be created. Click OK. Keynote Confidential 21

22 Installation Guide 6 Right-click the newly created database and select Tasks > Restore > Database. 7 In the Restore Database dialog box, select From device. 22 Keynote Confidential

23 Installation Guide 8 Click the ellipsis button next to From device to specify the backup medium. The Specify Backup dialog box is displayed. 9 Select File from the drop-down list and click Add. 10 In the Locate Backup File dialog box, select the database backup file and click OK. Keynote Confidential 23

24 Installation Guide 11 The file is now listed in the Specify Backup dialog box. Click OK. 12 In the Restore Database dialog box, check Restore next to the selected database backup file. 24 Keynote Confidential

25 Installation Guide 13 In the Options tab, check Overwrite the existing database. Also ensure that you are pointing to the correct path of the database MDF and LDF files (Restore As ellipsis buttons). 14 Click OK to restore the database. 15 Now that you have successfully installed the database, you must refresh it in order to see it listed in the Object Explorer Configuring the Database You must configure the database to allow the Access Server and the Portal server to communicate with it. 1 Launch SQL Server Configuration Manager, e.g., Start > All Programs > Microsoft SQL Server 2008 R2 > Configuration Tools > SQL Server Configuration Manager. Keynote Confidential 25

26 Installation Guide 2 Select Client Protocols. Ensure that the protocols for your database are enabled (right-click a protocol and select Enable). 3 Restart the SQL Server (MSSQLSERVER) service. The database is now configured to allow communication from the Access Server and the Portal server. 4.2 DOM Server For using Web commands, the communication channel between the web page served to the device and DeviceAnywhere Studio is routed through a central server called the DOM Server. DeviceAnywhere Studio establishes a secondary communication channel using a small JavaScript routine running inside the test web page. This enables extraction of the DOM to facilitate scripting and injection of commands (e.g., clicking on a link) during test execution Installing the DOM Server To install the DOM Server: 1 Double-click the DOM Server installer (DeviceAnywhereWebTest.exe) and if necessary, click Run to execute it. You can only install the DeviceAnywhere DOM Server on 64-bit machines. 2 Click Next on the Setup screen that appears. 26 Keynote Confidential

27 Installation Guide 3 Accept the license terms and click Next. 4 Choose a destination folder and select Next. This will begin the installation of the DOM Server. The default file location is C:\DeviceAnywhere\WebTest. You may enter a different location if desired. Do not use spaces in the installation path the service is not installed correctly if you do so. Keynote Confidential 27

28 Installation Guide 5 In the configuration screen, fill out information as shown in the table below and click Next. Field Server Address Port SSL Port Prompt MCD Value DOM Server IP/hostname DOM Server incoming port 80 (Default Change if different.) DOM Server incoming SSL port 443 (Default Change if different.) NOTE Both the Port and SSL Port need to be defined in order to navigate to secure test web pages. Check if you want to be prompted to enter the device MCD manually when defining or executing Web commands on a device. The prompt only appears if the system is not able to register the device MCD automatically with the DOM Server. 28 Keynote Confidential

29 Installation Guide 6 Click Finish to complete DOM Server installation Verifying DOM Server Installation. Check that the Windows MC Keynote Webtest service has been started. Figure 4-1 Verifying DOM Server Service Keynote Confidential 29

30 Installation Guide Log files available at C:\DeviceAnywhere\WebTest\logs should also read Service KeynoteWebTest installed. Figure 4-2 DOM Server Log File 4.3 Access Server The Access Server controls the environment by controlling all communication between other servers and the database. The Access Server manages the data generated from DeviceAnywhere Studio and stored in the SQL Server database. There can only be one Access Server per environment. All users and servers in the environment must be able to connect to the Access Server. The Access Server can be viewed as a thin layer providing authentication and synchronization between the other servers and the central database Connectivity Requirements The Access Server has following connectivity requirements: The Access Server must be able to connect to the Database Server. DeviceAnywhere Studio users must be able to connect to the Access Server using its IP address or machine name appended with the Access Server port (this documented in DeviceAnywhere Studio Installation for Windows). All other server components such as the Portal and distributed Ensemble Servers must be able to connect to the Access Server using its IP address or hostname Installing the Access Server To install the Access Server: 1 Double-click the Access Server installer (AccessServer.exe for 32-bit systems, AccessServer64.exe for 64-bit systems) and if necessary, click Run to execute it. 2 Click Next on the Setup screen that appears. 30 Keynote Confidential

31 Installation Guide 3 Accept the license terms and click Next. Keynote Confidential 31

32 Installation Guide 4 Choose a destination folder and select Next. This will begin the installation of the Access Server. The default file location is C:\Program Files\DeviceAnywhere\AccessServer. You may enter a different location if desired. 5 It may take a few minutes as components are installed and you see the configuration screen (page 1 of 2). Fill out configuration information as shown in the table below and click Next. Field Database Address Port Database Name Username Password External Address Port SSL Port Enable ABBY Support Value Database server IP/hostname Database port--access Server connects to database using this port (Default change if different.) Name of the database on the database server this is the database created in section Database server login ID NOTE The Access Server and Portal use JDBC to connect to the database server. This requires SQL Server Authentication. Provide a user ID and password with the proper SQL Server Authentication permissions. This is most likely the sa account unless your database has been set up with a different name. Database Server password reconfirm the password. Access Server IP/hostname Access Server port 443 (Default Change if different.) Access Server SSL port Optional check and provide a port number. Checked by default to enable ABBYY text recognition. Contact your Keynote Solutions Consultant if you want to obtain a license for this feature. 32 Keynote Confidential

33 Installation Guide Field Web Hosting Port Base URL Facade Value Reserved for web services Portal uses this port to communicate with the Access Server (Default) URL of the DOM Server Protocol do not change. 6 In the second configuration screen, enter configuration information as shown in the table below and click Next. Field Address Port SSL Port Result Portal URL BluePrint Portal URL Mail Server Address Mail Server Port Value IP/Hostname of server on which the Portal is to be installed (omit protocol, e.g., localhost) Portal port 80 (Default--Change if different.) Enterprise Portal SSL port check to enable and enter a port number. IMPORTANT The default is 443 change (to 0) if assigned to the Access Server and if installing the Portal on the same machine as the Access Server. Enter a URL to access the Results Portal directly Enter if you want to configure your environment to use the shared Portal. SMTP Mail server IP/Hostname Mail server port 25 (Default) Keynote Confidential 33

34 Installation Guide NOTE You can change the Access Server configuration later if required. 7 Click Finish to complete the Access Server installation Verifying Access Server Installation When the Access Server is successfully installed and configured, the Access Server log is found at the following path: C:\Program Files\DeviceAnywhere\Access Server\logs\log.txt 34 Keynote Confidential

35 Installation Guide You can view the log of the Access Server using a real-time log monitor (such as the Tail utility). To verify installation, check in the log that the Access Server is properly initialized with build date and database information clearly displayed (see the highlighted section in the figure below). There should be no exceptions before this information is displayed. Figure 4-3 Sample Access Server Log If there are errors, correct them and restart the Access Server. 4.4 IIS Web Server Internet Information Services (IIS), formerly called Internet Information Server, is a Web server application and set of feature extension modules created by Microsoft for use with Microsoft Windows. Internet Information Services (IIS) 6.0 makes it easy to share documents and information across a company intranet or the Internet. IIS 6.0 is the fastest Web server for Windows 2003 Server Installing and Configuring IIS Use the procedures below to install and configure IIS on: Windows versions prior to Vista Windows Vista and later versions Installing IIS on Windows Versions Prior to Vista 1 Insert a Windows installation CD into your server s CD-ROM drive. 2 On the machine where the Portal is to be deployed, navigate to the Control Panel: Start > Settings > Control Panel. 3 Select Add/Remove Windows Components. 4 Double-click Application Server. Keynote Confidential 35

36 Installation Guide 5 Select Internet Information Server (IIS) and click OK. 36 Keynote Confidential

37 Installation Guide The Windows Component Wizard indicates that it is configuring server components. 6 Click Finish to complete installation and exit the wizard. Installing IIS on Windows Vista and Later 1 On the machine where the Portal is to be deployed, navigate to the Control Panel: Start > Control Panel. Keynote Confidential 37

38 Installation Guide 2 Select Programs. 3 Select Turn Windows features on or off. 4 Select and expand Internet Information Services from the Windows Features window. 38 Keynote Confidential

39 Installation Guide 5 Select and expand World Wide Web Services from the Internet Information Services components listed. 6 Select and expand Application Development Features. 7 Select the ASP and ASP.NET components (other components are automatically selected). Keynote Confidential 39

40 Installation Guide 8 In the Common HTTP Features section of World Wide Web Services, ensure that Static Content is selected. 9 When the components have been enabled, click OK to complete your IIS installation Verifying IIS Server Installation To check that IIS is running in Internet Information Services console: 1 Select Start > Run. 2 Enter the command inetmgr; this will open the Internet Information Services (IIS) Manager. 3 Navigate to Web Sites > Default Web Site. 40 Keynote Confidential

41 Installation Guide 4 Click the Run button if IIS is not running. 4.5 Portal The Portal provides access to test results. You can also access customer, user, and device administration. The Portal combines the installers and functionalities of the MyDeviceAnywhere (Mobile Harmony) Server and the Results Portal Connectivity Requirements The Portal has following connectivity requirements: The Portal must be able to connect to the Database Server. The Portal must be able to connect to the Access Server. The Portal must be able to connect to the SMTP Server. In order to use the DeviceAnywhere Portal, you must be able to access the server hosting it by entering the URL of the Portal, e.g., Installing the DeviceAnywhere Portal To install the DeviceAnywhere Portal: 1 Double-click the EnterprisePortal.exe installer to execute it. Keynote Confidential 41

42 Installation Guide 2 In the Setup screen that appears, click Next. 3 Accept license terms and select Next. 42 Keynote Confidential

43 Installation Guide 4 In the Destination Location screen, choose an installation location for the DeviceAnywhere Portal and click Next. The default destination folder is C:\Program Files\DeviceAnywhere\Portals. NOTE You may install the Portal at another location. 5 In the configuration screen, enter configuration information as shown in the table below. Select Next. Field Server Address Value Hostname/IP address of the server hosting the Portal Keynote Confidential 43

44 Installation Guide Field Server Port Is Secure Certificate Database Address Database Name Username Password Value Portal port 80 (Default change if different.) Check to use HTTPS to connect to the Portal. Choose a security certificate from the drop-down list. Or click Import to import a certificate and then select it from the Certificate drop-down list. Database Server IP/hostname Name of the database created in section on the Database server Database server login ID with SQL Server Authentication permissions NOTE The Access Server and Portal use JDBC to connect to the Database server. This requires SQL Server Authentication. Provide a user ID and password with the proper SQL Server Authentication permissions. This is most likely the sa account unless your database has been set up with a different name. Database Server password reconfirm the password. 6 In the second configuration screen, enter configuration information as shown in the table below and click Next. Field Access Server Address Access Server Port External Authentication Mail Server Address Value Access Server IP/hostname 443 (Default Change if different.) Check to use your own authentication for users and provide the name/ip address of the authentication server in the field below. SMTP server IP/hostname A screen indicates the progress of the configuration while several Windows components are installed: 44 Keynote Confidential

45 Installation Guide.NET Framework 4.0 Microsoft ASP.NET 2.0 AJAX Extensions 1.0 Microsoft WSE 3.0 This may take several moments. 7 Click Finish to exit the Portal installation wizard. 4.6 License File To install a license file: 1 After you have installed the Portal and a customer account has been created for you on the portal, contact your Keynote Solutions Consultant to procure a license file (see the figure below) in XML format. 2 Copy this XML file to the Access Server license folder, located by default at the following location: C:\Program Files\DeviceAnywhere\AccessServer\config\license. 3 Wait till midnight for the license file to take effect. You can also restart the Access Server for the license file to take effect immediately. Keynote Confidential 45

46 Installation Guide Figure 4-4 License File 4.7 LiveTest or LiveMonitor Server The LiveTest and LiveMonitor Servers enable you to execute scheduled test runs and monitor scripts, respectively Connectivity Requirements The LiveTest Server has following connectivity requirements: The LiveTest Server must be able to connect to the Access Server. The LiveTest Server must be able to connect to the Portal. The LiveTest Server must be able to connect to the SMTP Server. The LiveTest Server must be able to connect to the DOM Server Installing LiveTest Server To install the LiveTest or LiveMonitor Server (these steps use the LiveTest Server for illustration): 1 Double-click the LiveTest Server (LiveTest.exe for 32-bit systems, LiveTest64.exe for 64-bit systems) or LiveMonitor Server (LiveMonitor.exe for 32-bit systems, LiveMonitor64.exe for 64-bit systems) installer and if necessary, click Run to execute it. 2 Click Next on the Setup screen that appears. 46 Keynote Confidential

47 Installation Guide 3 Accept the license terms and click Next. 4 Choose a destination folder and select Next. This will begin the installation of the LiveTest (LiveMonitor) Server. The default installation location for the LiveTest Server is C:\Program Files\DeviceAnywhere\LiveTest. You may enter a different location if desired. Keynote Confidential 47

48 Installation Guide 5 It may take a few minutes as components are installed and you see the configuration screen (page 1 of 2). Fill out configuration information as shown in the table below and click Next. Field External Address Value LiveTest server IP/hostname 48 Keynote Confidential

49 Installation Guide Field Location Port SSL Port (Access Server) Address Port SSL Port Address Port SSL Port Value Enter a location; this appears DeviceAnywhere Studio and the Enterprise Portal. LiveTest Server service port 0 (Default change to actual value, e.g., 448 or 446.) 0 (Default do not change.) Access Server IP/hostname Access Server port 0 (Default Change if different.) Access Server port 0 (Default Change if different.) NOTE Provide either the Port or SSL Port number for the Access Server. Hostname/IP address of the Portal Enterprise Portal port 0 (Default Change if different.) Enterprise Portal SSL port 443 (Default Change if different.) NOTE Provide either the Port or SSL Port number for the Enterprise Portal. 6 In the second configuration screen, enter configuration information as shown in the table below and click Next. Field Address Value SMTP Mail server IP/Hostname Keynote Confidential 49

50 Installation Guide Field Port Connect to the Internet directly Use a proxy server Address Port User Name Password WebProxy URL Value Mail server port 25 (Default) Select if not using a proxy server selected by default. Not supported URL of the DeviceAnywhere DOM Server 7 Click Finish to complete the LiveTest Server installation Verifying LiveTest Server Installation Check that the MC LiveTest service has been started. When installing the LiveMonitor Server, check that the MC LiveMonitor service has been started. 4.8 Ensemble Server The Ensemble Server hosts one or more devices over USB, Wi-Fi, or Bluetooth. Each Server typically hosts 2 6 devices. You will need to repeat this installation procedure for each Ensemble Server in your DeviceAnywhere test environment. See DeviceAnywhere Ensemble Server Guidelines for installation guidelines and connectivity requirements. 50 Keynote Confidential

51 Installation Guide Ensemble Server Guidelines Devices A typical Ensemble Server supports up to four devices. Tablets and other high-resolution, large-screen devices require more processing power than other smartphones for data transfer; an Ensemble Server might need to host a maximum of two tablets or four smartphones. In addition, the number of devices being used concurrently as well as the type of operations being performed (e.g., image comparisons) can impact the number of devices that can be supported. Connectivity Requirements Ensemble Servers have following connectivity requirements: Ensemble Servers must be able to connect to the Access Server. Devices must be connected to the Ensemble Server machine. DeviceAnywhere Studio users must be able to connect to the Ensemble Servers. IMPORTANT If access to devices over the Internet is required, the Ensemble Servers need an external IP addresses. Contact your Keynote Solutions Consultant to help determine the proper device allocation on each Ensemble Server for your specific deployment Ensemble Server Installation Before installation, you must gather the following information: The IP address or hostname of your Access Server Access Server port (if different from the default) The credentials of a DeviceAnywhere account in your test environment with permission to use Ensemble Server and connect to the Access Server The IP address or hostname you wish to assign to the Ensemble Server License key and password for using the ABBYY text recognition engine (contact your TAM for assistance) To install the Ensemble Server: 1 Double-click the EnsembleServer.exe installer to execute it. Keynote Confidential 51