DeviceAnywhere Enterprise Private System

DeviceAnywhere Enterprise Private System
DeviceAnywhere Enterprise
Private System Installation Guide
Release 6.0
DeviceAnywhere Enterprise
Installation Guide
DeviceAnywhere Enterprise 6.0
June 2013
Copyright Notice
Copyright © 1995-2013 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 94404
ii
Keynote Confidential
Installation Guide
DeviceAnywhere Enterprise
Contents
About This Document ...................................................................................................... 5
Document Outline ........................................................................................................................................ 5
Typographical Conventions........................................................................................................................ 6
Contacting Support ...................................................................................................................................... 6
Additional Documentation ......................................................................................................................... 6
1
2
3
4
Introduction ............................................................................................................ 7
1.1
Components .................................................................................................................................... 7
1.2
General Installation Guidelines.................................................................................................... 8
Infrastructure Requirements ................................................................................ 9
2.1
System Size and Topology ............................................................................................................ 9
2.2
Overview ....................................................................................................................................... 10
2.3
System Requirements .................................................................................................................. 10
2.4
Mobile Device Requirements...................................................................................................... 12
2.4.1
Hardware-Integrated Devices ...................................................................................... 12
2.4.2
Local Software Devices ................................................................................................. 13
2.5
Rack Space Requirements ........................................................................................................... 13
2.6
Power ............................................................................................................................................. 15
2.7
Operating Conditions .................................................................................................................. 16
2.8
Database Backup Requirements ................................................................................................. 16
2.9
High Availability Requirements ................................................................................................ 16
2.10
Network and Port Requirements ............................................................................................... 16
Network Configuration and Tests .................................................................... 17
3.1
Connectivity Requirements ....................................................................................................... 17
3.2
Anti-Virus Settings ...................................................................................................................... 17
3.3
Test Procedures ............................................................................................................................ 17
3.3.1
Opening a Telnet Session to Test the Connection ..................................................... 17
3.3.2
Server Connectivity Tests ............................................................................................. 18
Component Installation ...................................................................................... 19
4.1
DeviceAnywhere Enterprise Database ..................................................................................... 19
4.1.1
Pre-requisites for Installation ....................................................................................... 19
4.1.2
Creating and Restoring a Database in SQL Server 2008 ........................................... 19
4.1.3
Configuring the Database ............................................................................................. 25
4.2
DeviceAnywhere Enterprise DOM Server ............................................................................... 26
4.2.1
Installing the DOM Server ............................................................................................ 26
4.2.2
Verifying DOM Server Installation. ............................................................................ 29
4.3
Access Server ................................................................................................................................ 30
Keynote Confidential
iii
DeviceAnywhere Enterprise
Installation Guide
4.3.1
4.3.2
4.3.3
Connectivity Requirements .......................................................................................... 30
Installing the Access Server .......................................................................................... 30
Verifying Access Server Installation ........................................................................... 34
5
iv
4.4
IIS Web Server .............................................................................................................................. 35
4.4.1
Installing and Configuring IIS ..................................................................................... 35
4.4.2
Verifying IIS Server Installation................................................................................... 40
4.5
DeviceAnywhere Enterprise Portal ........................................................................................... 41
4.5.1
Connectivity Requirements .......................................................................................... 41
4.5.2
Installing the DeviceAnywhere Portal ........................................................................ 41
4.6
License File .................................................................................................................................... 45
4.7
LiveTest or LiveMonitor Server ................................................................................................. 46
4.7.1
Connectivity Requirements .......................................................................................... 46
4.7.2
Installing LiveTest Server ............................................................................................. 46
4.7.3
Verifying LiveTest Server Installation ........................................................................ 50
4.8
Ensemble Server ........................................................................................................................... 50
4.8.1
Ensemble Server Guidelines ......................................................................................... 51
4.8.2
Ensemble Server Installation ........................................................................................ 51
4.8.3
Verifying Ensemble Server Installation ...................................................................... 60
4.9
DeviceAnywhere Studio ............................................................................................................. 60
4.9.1
Connectivity Requirements .......................................................................................... 61
4.9.2
Installing DeviceAnywhere Studio on Windows ...................................................... 61
4.9.3
Installing DeviceAnywhere Studio on Mac OS X...................................................... 64
4.10
Mobile Devices ............................................................................................................................. 64
4.10.1 Provisioning Packages with Devices ........................................................................... 65
4.10.2 Assigning Packages to User Groups ........................................................................... 66
4.10.3 Verifying Device Installation........................................................................................ 67
System Verification ............................................................................................. 68
5.1
Restarting the Access Server ....................................................................................................... 68
5.2
Verifying DeviceAnywhere Functionality ................................................................................ 69
Keynote Confidential
Installation Guide
DeviceAnywhere Enterprise
About This Document
This DeviceAnywhere Enterprise Installation Guide outlines the requirements and procedures for installing a
DeviceAnywhere Enterprise test or monitoring environment. With DeviceAnywhere Enterprise, 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 DeviceAnywhere Enterprise 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 DeviceAnywhere Enterprise 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 DeviceAnywhere Enterprise 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

DeviceAnywhere Enterprise 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 DeviceAnywhere Enterprise test
environment.
Keynote Confidential
5
DeviceAnywhere Enterprise
Installation Guide
Typographical Conventions
The table below describes the typographical conventions used in DeviceAnywhere documentation.
Style
Element
Examples
Blue
Links and email addresses
http://www.keynotedeviceanywhere.com
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 DeviceAnywhere Enterprise
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 http://support.keynote.com or 1-888-KEY-SYST
(539-7978).
Additional Documentation
You can find additional documentation on test automation at
http://www.keynotedeviceanywhere.com/testing-automation-documentation.html.
Enterprise test automation customers with private devices can find additional documentation at
http://www.keynotedeviceanywhere.com/dae-pvt-devices-documentation.html.
Monitoring customers can find information at http://www.keynotedeviceanywhere.com/monitoringdocumentation.html.
You can access the documentation web page for your environment from the Help menu in
DeviceAnywhere Studio.
6
Keynote Confidential
Installation Guide
1
DeviceAnywhere Enterprise
Introduction
This chapter lists the components required for installing a DeviceAnywhere Enterprise 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
DeviceAnywhere Enterprise environment:

DeviceAnywhere Enterprise 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.

DeviceAnywhere Enterprise 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 DeviceAnywhere Enterprise environment

DeviceAnywhere Enterprise Portal —Web portal for managing user accounts and test results

EnterprisePortal_MA.exe for DeviceAnywhere Enterprise Automation

EnterprisePortal_TA.exe for DeviceAnywhere Enterprise Monitoring

DeviceAnywhere Enterprise 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 http://www.keynotedeviceanywhere.com/dae-pvt-devicesdocumentation.html.
NOTE Components of a DeviceAnywhere Enterprise environment require a network connection to
communicate with each other.
The following components are automatically installed with the DeviceAnywhere Enterprise Portal:

.NET 4 runtime framework

Microsoft ASP .NET AJAX Extension (ASP AJAX 1.0)
Keynote Confidential
7
DeviceAnywhere Enterprise

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
DeviceAnywhere Enterprise database
For specific information on SQL Server installation, refer to Microsoft SQL Server documentation.

IIS Server v6 or 7 on the machine hosting the DeviceAnywhere Enterprise Portal

JDK 1.5+ if installing DeviceAnywhere Studio on Macintosh machines
1.2
General Installation Guidelines
Start Here—before attempting to install a DeviceAnywhere Enterprise 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.
DeviceAnywhere Enterprise components are installed in this order:
1
SQL Server 2008 and DeviceAnywhere Enterprise database
2
DeviceAnywhere Enterprise DOM Server (if not using Keynote’s DOM Server)
3
Access Server
4
DeviceAnywhere Enterprise 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
Installation Guide
2
DeviceAnywhere Enterprise
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 DeviceAnywhere Enterprise environment.
When you have finished reviewing this section, you should be able to set up and connect the hardware
components of your DeviceAnywhere Enterprise installation.
2.1
System Size and Topology
Keynote supports deploying DeviceAnywhere Enterprise 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
Description
Small
A small deployment contains from 2 – 4 devices attached to an Ensemble Server.
 Computer 1 = SQL Server and DeviceAnywhere Enterprise database, Access Server,
DeviceAnywhere Enterprise Portal
 Computer 2 = LiveTest or LiveMonitor Server + DeviceAnywhere Enterprise 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 DeviceAnywhere Enterprise database
 Computer 2 = DeviceAnywhere Enterprise DOM Server
 Computer 3 = Access Server, DeviceAnywhere Enterprise 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
DeviceAnywhere Enterprise
2.2
Installation Guide
Overview
Depending on the number of devices and locations in your DeviceAnywhere Enterprise 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 DeviceAnywhere Enterprise
components are:
Table 2-2 Minimum System Requirements for Individual Components
DA Component
Hardware/Software
Requirement
Database Server
Processor speed


DeviceAnywhere DOM
Server
10
Notes
Core i5 for DeviceAnywhere
Enterprise Automation
Quad core (e.g., Xeon) for
DeviceAnywhere Enterprise
Monitoring
Memory


4 GB RAM for automation
8 GB for monitoring (16 GB
recommended)
Hard drive space
250 GB (as needed)
Database
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
Memory
4 GB RAM
Hard drive space
40 GB
Operating system


Windows Server 2003
Windows 7
Keynote Confidential
Installing this yourself
is optional; you can
use Keynote’s DOM
Server instead—
contact your Solutions
Consultant.
Installation Guide
DA Component
DeviceAnywhere Enterprise
Hardware/Software
Requirement
Notes
 Windows Server 2008
Only 64-bit processing supported.
Access Server
DeviceAnywhere
Enterprise Portal
LiveTest or LiveMonitor
Server
Ensemble Server
Processor speed


Core i5 for automation
Core i7 for monitoring
Memory
4 GB RAM (8 GB recommended)
Hard drive space
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.
Processor speed
Core i3
Memory
4 GB RAM
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




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
Core i5
Memory
4 GB RAM
Hard drive space
200 GB
Operating system
 Windows Server 2003
 Windows Server 2008
64-bit processing is required because of
memory requirements.
50 concurrent users
100 concurrent users
supported (only 10 on
Windows XP)
Google Chrome
Internet Explorer
Firefox
Safari
Processor speed
Core i3
Memory
3 or 4 GB RAM
Hard drive space
10 GB
Operating system
 Windows XP
 Windows Server 2003
 Windows 7
 Windows Server 2008
Ensemble Server is compatible with
Windows 7 x64. Only x86 supported on
other Windows systems. You cannot avail
of more than 4 GB RAM on x86 machines.
Keynote Confidential


Maximum of 2 – 4
concurrently
attached devices
supported.
Install this
component on a
separate machine
from other server
components for
optimum
performance.
11
DeviceAnywhere Enterprise
DA Component
DeviceAnywhere Studio
Installation Guide
Hardware/Software
Requirement
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.
Processor speed
2 GHz dual core (Pentium 4 or higher)
Memory
2 GB RAM
Hard drive space
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
Additional


Optional:
DeviceAnywhere Addin for UFT
Notes
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 DeviceAnywhere Enterprise 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.
2.4.1 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
Installation Guide

DeviceAnywhere Enterprise
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 DC @ 3A (12W). iPad devices
have a 12V power supply.
Keynote provides the required USB cables.
2.4.2 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 http://www.keynotedeviceanywhere.com/daepvt-devices-documentation.html.

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 http://www.racksolutions.com/server-racks-cabinets-enclosures.html.
The rack units needed for each DeviceAnywhere Enterprise component is given in the table below.
Table 2-3 Rack Space Requirements
Server/Client Computers
Description
SQL Server and database
2U rack mountable-server
Access Server, DeviceAnywhere
Enterprise Portal
2U rack mountable-server
Ensemble Server
1U or 2U rack-mountable server (must support USB cards)
Device (hardware integrated)
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.
PDU
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
DeviceAnywhere Enterprise
Installation Guide
Figure 2-1 Rack Front and Side Views
Front View
Side View
Device 3
Device 3
Device 2
Device 2
Device 1
Device 1
Device 4
PDU
Ensemble 5
Space for cable runs
Ensemble Server 5
Space for cable runs
Device 3
Device 3
Device 5
Device 2
Device 2
Device 4
Device 1
Device 1
PDU
Space
Ensemble 4
Ensemble Server 4
Device 3
Device 5
Device 2
Device 2
Device 4
Device 1
Device 1
42 U
Device 3
Ensemble Server 3
PDU
Space
Ensemble 3
Device 3
Device 1 (tablet)
Device 1
PDU
Ensemble 2
Space for cable runs
Ensemble Server 2
Space for cable runs
Device 3
Device 3
Device 5
Device 2
Device 2
Device 4
Device 1
Device 1
PDU
Space
Ensemble 1
Ensemble Server 1
Access
DB Server
DB
UPS
UPS
2U
Access Server
19"
14
Device 2
27 7/8"
Keynote Confidential
Installation Guide
DeviceAnywhere Enterprise
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
DeviceAnywhere Enterprise
2.7
Installation Guide
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
DeviceAnywhere Enterprise 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.
2.10
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
The Access Server and the DeviceAnywhere Portal communicate with
the database. The default SQL Server port is 1433.
1433
Access Server
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.
443
6232 –
Reserved for
future Web
services
DeviceAnywhere
Enterprise Portal
The DeviceAnywhere Enterprise 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.
80
Ensemble Server
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.
443 - In
443 - Out
DeviceAnywhere Studio
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.
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
Installation Guide
3
DeviceAnywhere Enterprise
Network Configuration and Tests
Once you have set up the hardware for your DeviceAnywhere Enterprise 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 DeviceAnywhere Enterprise installation:

The Access Server and DeviceAnywhere Enterprise Portal must be able to connect to the
DeviceAnywhere Enterprise 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 DeviceAnywhere Enterprise 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 DeviceAnywhere Enterprise environment are configurable. Consult your
Keynote Solutions Consultant for further information on using non-default ports.
3.3
Test Procedures
Before installing DeviceAnywhere Enterprise 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 DeviceAnywhere Enterprise installation.
3.3.1 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
DeviceAnywhere Enterprise
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 www.deviceanywhere.com/enterprise-documentation.html on port 443.
Repeat this procedure to run all the tests listed in Table 3-1 below.
Figure 3-1 Telnet Error Message
3.3.2 Server Connectivity Tests
Table 3-1 DeviceAnywhere Enterprise 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> 443
DOS command prompt
window appears blank.
2
Action: Open a Telnet session from one of the client machines to port 80
on the machine that will host the DeviceAnywhere Enterprise Portal.
Command: telnet <Portal_Server_IP> 80
DOS command prompt
window appears blank.
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> 443
DOS command prompt
window appears blank.
4
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> 1433
DOS command prompt
window appears blank.
5
Action: Open a Telnet session from the DeviceAnywhere Enterprise
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.
18
Keynote Confidential
Installation Guide
4
DeviceAnywhere Enterprise
Component Installation
This section describes the procedures for installing individual DeviceAnywhere Enterprise components
and devices to deploy the DeviceAnywhere Enterprise 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 DeviceAnywhere Enterprise DOM Server
3
Installing the Access Server
4
Installing and configuring IIS
5
Installing the DeviceAnywhere Enterprise 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
DeviceAnywhere Enterprise Database
This section contains the steps required to set up the DeviceAnywhere Enterprise SQL database.
4.1.1 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 DeviceAnywhere Enterprise Portal server to communicate with the
database.

The DeviceAnywhere Enterprise database backup file complete_da.bak
4.1.2 Creating and Restoring a Database in SQL Server 2008
You must first create a new database and then restore the DeviceAnywhere Enterprise database.
1
Place the DeviceAnywhere Enterprise database backup file in an appropriate location on the database
server, e.g., C:/DA Databases/<DABackupFile>.bak.
Keynote Confidential
19
DeviceAnywhere Enterprise
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
Installation Guide
DeviceAnywhere Enterprise
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
DeviceAnywhere Enterprise
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
Installation Guide
DeviceAnywhere Enterprise
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
DeviceAnywhere Enterprise
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
Installation Guide
DeviceAnywhere Enterprise
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.
4.1.3 Configuring the Database
You must configure the database to allow the Access Server and the DeviceAnywhere Enterprise 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
DeviceAnywhere Enterprise
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 DeviceAnywhere Enterprise Portal server.
4.2
DeviceAnywhere Enterprise 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 DeviceAnywhere Enterprise 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.
4.2.1 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
Installation Guide
DeviceAnywhere Enterprise
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
DeviceAnywhere Enterprise
5
28
Installation Guide
In the configuration screen, fill out information as shown in the table below and click Next.
Field
Value
Server Address
DOM Server IP/hostname
Port
DOM Server incoming port
80 (Default—Change if different.)
SSL Port
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.
Prompt MCD
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 DeviceAnywhere Enterprise system is not able to register the device MCD
automatically with the DOM Server.
Keynote Confidential
Installation Guide
6
DeviceAnywhere Enterprise
Click Finish to complete DOM Server installation.
4.2.2 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
DeviceAnywhere Enterprise
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 DeviceAnywhere Enterprise 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 DeviceAnywhere Enterprise 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.
4.3.1 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 DeviceAnywhere Enterprise server components such as the DeviceAnywhere Enterprise
Portal and distributed Ensemble Servers must be able to connect to the Access Server using its IP
address or hostname.
4.3.2 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
Installation Guide
3
DeviceAnywhere Enterprise
Accept the license terms and click Next.
Keynote Confidential
31
DeviceAnywhere Enterprise
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.
32
Field
Value
Database Address
Database server IP/hostname
Port
Database port--Access Server connects to database using this port.
1433 (Default—change if different.)
Database Name
Name of the database on the database server—this is the database created in
section 4.1.2.
Username
Database server login ID
NOTE The Access Server and DeviceAnywhere Enterprise 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.
Password
Database Server password—reconfirm the password.
External Address
Access Server IP/hostname
Port
Access Server port
443 (Default—Change if different.)
SSL Port
Access Server SSL port
Optional—check and provide a port number.
Enable ABBY Support
Checked by default to enable ABBYY text recognition. Contact your Keynote
Solutions Consultant if you want to obtain a license for this feature.
Keynote Confidential
Installation Guide
6
DeviceAnywhere Enterprise
Field
Value
Web Hosting Port
Reserved for web services—DeviceAnywhere Enterprise Portal uses this port to
communicate with the Access Server.
6232 (Default)
Base URL
URL of the DeviceAnywhere Enterprise DOM Server
Facade
Protocol—do not change.
In the second configuration screen, enter configuration information as shown in the table below and
click Next.
Field
Value
Address
IP/Hostname of server on which the DeviceAnywhere Enterprise Portal is to be
installed (omit protocol, e.g., localhost)
Port
Portal port
80 (Default--Change if different.)
SSL Port
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.
Result Portal URL
Enter a URL to access the Results Portal directly—
http://<Portal_IP/Hostname>/ResultPortal
BluePrint Portal URL
Enter http://portal.deviceanywhere.com if you want to configure your
environment to use the shared DeviceAnywhere Enterprise Portal.
Mail Server Address
SMTP Mail server IP/Hostname
Mail Server Port
Mail server port
25 (Default)
Keynote Confidential
33
DeviceAnywhere Enterprise
Installation Guide
NOTE You can change the Access Server configuration later if required.
7
Click Finish to complete the Access Server installation.
4.3.3 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
Installation Guide
DeviceAnywhere Enterprise
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.
4.4.1 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 DeviceAnywhere Enterprise 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
DeviceAnywhere Enterprise
5
36
Installation Guide
Select Internet Information Server (IIS) and click OK.
Keynote Confidential
Installation Guide
DeviceAnywhere Enterprise
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 DeviceAnywhere Enterprise Portal is to be deployed, navigate to the
Control Panel: Start > Control Panel.
Keynote Confidential
37
DeviceAnywhere Enterprise
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
Installation Guide
DeviceAnywhere Enterprise
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
DeviceAnywhere Enterprise
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.
4.4.2 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
Installation Guide
4
Click the Run button
4.5
DeviceAnywhere Enterprise
if IIS is not running.
DeviceAnywhere Enterprise Portal
The DeviceAnywhere Enterprise Portal provides access to test results. You can also access customer, user,
and device administration. The DeviceAnywhere Enterprise Portal combines the installers and
functionalities of the MyDeviceAnywhere (Mobile Harmony) Server and the Results Portal.
4.5.1 Connectivity Requirements
The DeviceAnywhere Enterprise Portal has following connectivity requirements:

The DeviceAnywhere Enterprise Portal must be able to connect to the Database Server.

The DeviceAnywhere Enterprise Portal must be able to connect to the Access Server.

The DeviceAnywhere Enterprise 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., http://localhost.
4.5.2 Installing the DeviceAnywhere Portal
To install the DeviceAnywhere Portal:
1
Double-click the EnterprisePortal.exe installer to execute it.
Keynote Confidential
41
DeviceAnywhere Enterprise
Installation Guide
2
In the Setup screen that appears, click Next.
3
Accept license terms and select Next.
42
Keynote Confidential
Installation Guide
4
DeviceAnywhere Enterprise
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
Value
Server Address
Hostname/IP address of the server hosting the DeviceAnywhere Enterprise Portal
Keynote Confidential
43
DeviceAnywhere Enterprise
6
Installation Guide
Field
Value
Server Port
Portal port
80 (Default—change if different.)
Is Secure
Check to use HTTPS to connect to the Portal.
Certificate
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 Address
Database Server IP/hostname
Database Name
Name of the database created in section 4.1.2 on the Database server
Username
Database server login ID with SQL Server Authentication permissions
NOTE The Access Server and DeviceAnywhere Enterprise 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.
Password
Database Server password—reconfirm the password.
In the second configuration screen, enter configuration information as shown in the table below and
click Next.
Field
Value
Access Server Address
Access Server IP/hostname
Access Server Port
443 (Default—Change if different.)
External
Authentication
Check to use your own authentication for users and provide the name/IP address of
the authentication server in the field below.
Mail Server Address
SMTP server IP/hostname
A screen indicates the progress of the configuration while several Windows components are installed:
44
Keynote Confidential
Installation Guide
DeviceAnywhere Enterprise

.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 DeviceAnywhere Enterprise 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
DeviceAnywhere Enterprise
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.
4.7.1 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 DeviceAnywhere Enterprise Portal.

The LiveTest Server must be able to connect to the SMTP Server.

The LiveTest Server must be able to connect to the DeviceAnywhere Enterprise DOM Server.
4.7.2 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
Installation Guide
DeviceAnywhere Enterprise
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
DeviceAnywhere Enterprise
5
48
Installation Guide
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
Value
External Address
LiveTest server IP/hostname
Keynote Confidential
Installation Guide
6
DeviceAnywhere Enterprise
Field
Value
Location
Enter a location; this appears DeviceAnywhere Studio and the Enterprise
Portal.
Port
LiveTest Server service port
0 (Default—change to actual value, e.g., 448 or 446.)
SSL Port
0 (Default—do not change.)
(Access Server) Address
Access Server IP/hostname
Port
Access Server port
0 (Default—Change if different.)
SSL Port
Access Server port
0 (Default—Change if different.)
NOTE Provide either the Port or SSL Port number for the Access Server.
Address
Hostname/IP address of the DeviceAnywhere Enterprise Portal
Port
Enterprise Portal port
0 (Default—Change if different.)
SSL Port
Enterprise Portal SSL port
443 (Default—Change if different.)
NOTE Provide either the Port or SSL Port number for the Enterprise Portal.
In the second configuration screen, enter configuration information as shown in the table below and
click Next.
Field
Value
Address
SMTP Mail server IP/Hostname
Keynote Confidential
49
DeviceAnywhere Enterprise
Installation Guide
Field
Value
Port
Mail server port
25 (Default)
Connect to the Internet directly
Select if not using a proxy server—selected by default.
Use a proxy server
Not supported
Address
Port
User Name
Password
WebProxy URL
7
URL of the DeviceAnywhere DOM Server
Click Finish to complete the LiveTest Server installation.
4.7.3 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
Installation Guide
DeviceAnywhere Enterprise
4.8.1 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.
4.8.2 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
DeviceAnywhere Enterprise
Installation Guide
2
Click Next in the Ensemble Server Setup screen that appears.
3
Accept the license terms and click Next.
52
Keynote Confidential
Installation Guide
4
DeviceAnywhere Enterprise
Choose a destination folder and select Next. This will begin the installation of the Ensemble Server.
The default file location is C:\Program Files(x86)\DeviceAnywhere\
EnsembleServer. You may enter a different location if desired.
The wizard indicates the progress of the installation.
Keynote Confidential
53
DeviceAnywhere Enterprise
5
54
Installation Guide
In the Ensemble Server configuration screen, enter configuration information as shown in the table
below and click Next.
Field
Value
Address
Access Server IP/Hostname
Port
The default port of the Access Server is 443—Change if different.
SSL Port
Access Server SSL port—the default port is 0. Change if different.
Location
Enter the name of the city, e.g., Paris, where the Ensemble Server is physically
located.
Port
Set the Ensemble Server port to 443—change if different.
Country
Enter the country, e.g., France, where this Ensemble Server is located.
External Address
Ensemble Server machine IP/hostname
Use the IP address or hostname assigned to the Ensemble Server machine.
The external address is the IP address or machine name that users and other system
components will use to communicate with the Ensemble Server.
Keynote Confidential
Installation Guide
6
DeviceAnywhere Enterprise
In the ABBY Configuration screen, select Use ABBY if you desire text recognition capabilities and can
provide license information. Your Keynote Solutions Consultant will provide your license
information or assist with procuring a license if you do not have one. Select Next.
NOTE ABBY is automatically installed with the Ensemble Server and the default program and
license file locations are displayed in this screen. You can change these values if you wish to point to
another installation of ABBYY.
A dialog box shows the progress of component installation.
7
Select Yes to install the Tone Decoder ActiveX Control. This enables the sound decoder that supports
audio reference points.
Keynote Confidential
55
DeviceAnywhere Enterprise
Installation Guide
8
In the Tone Decoder ActiveX Control installation wizard, select Next.
9
Accept the Tone Decoder ActiveX Control licensing terms.
56
Keynote Confidential
Installation Guide
DeviceAnywhere Enterprise
10 In the Select Destination Directory screen, choose an installation location for the Tone Decoder
ActiveX Control. The default destination is C:\Program Files(x86). You may choose another
location. Click Next.
11 Next, you must choose a location for the Tone Decoder’s shortcuts in the Start menu. Click Next to
install the shortcuts.
Keynote Confidential
57
DeviceAnywhere Enterprise
Installation Guide
12 Click Install to begin installation of the tone decoder.
13 Select Finish to complete installation of the Tone Decoder ActiveX Control.
58
Keynote Confidential
Installation Guide
DeviceAnywhere Enterprise
14 Click Finish to complete installing the Ensemble Server.
The MC EnsembleServer service is automatically started.
Keynote Confidential
59
DeviceAnywhere Enterprise
Installation Guide
4.8.3 Verifying Ensemble Server Installation
When you have successfully installed and configured the Ensemble Server, you can verify the installation.
Log files can be found at C:\Program Files\DeviceAnywhere\
EnsembleServer\logs.
Verify in the log file that:

The Ensemble Server has initialized loading data from Access Server.

The correct build version and date are displayed.

The Ensemble Server displays the heartbeat of any devices that are connected to it. A sample of the
log is shown in the figure below.
Figure 4-5 Ensemble Server to Access Server Connection
Figure 4-6 Ensemble Server Log with Build Number
Device heartbeats are shown in the image below:
Figure 4-7 Device Heartbeats
4.9
DeviceAnywhere Studio
DeviceAnywhere Studio is the client application that enables you to interact with devices and create
manual and automated tests in the Test Case Manager and Automation views. This section assumes you
are installing the DeviceAnywhere Studio for the first time.
Before installation, you must gather the following information:

60
The IP address and port of the Access Server in your test environment
Keynote Confidential
Installation Guide

DeviceAnywhere Enterprise
Login credentials for DeviceAnywhere Studio
4.9.1 Connectivity Requirements
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 (see Installing DeviceAnywhere Studio on
Windows below). If a user needs to access the test environment over the Internet, an external IP address
is required.
4.9.2 Installing DeviceAnywhere Studio on Windows
To install DeviceAnywhere Studio:
1
On the client machine, double-click the DeviceAnywhereStudioEnt.exe installer and click Run
to execute it.
2
In the DeviceAnywhere Studio setup screen that appears, click Next.
Keynote Confidential
61
DeviceAnywhere Enterprise
Installation Guide
3
Accept the license terms and click Next.
4
Choose an installation location in the local directory for DeviceAnywhere Studio. By default, this
folder is C:\Program Files(x86)\DeviceAnywhere\DeviceAnywhereStudio. (User-specific
information such as workspace and profile information will be saved to
C:\Users\<Windows_user_name>\AppData\Local\DeviceAnywhere.) Click Next. This
initiates installation.
62
Keynote Confidential
Installation Guide
5
6
DeviceAnywhere Enterprise
In the configuration screen, provide DeviceAnywhere Studio configuration information as shown in
the table below and click Next.
Field
Value
Address
Access Server IP/hostname appended with port, e.g., 10.100.100.143:443
NOTE The default communication port on the Access Server is 443.
Select Run DeviceAnywhere Studio now and click Finish.
Keynote Confidential
63
DeviceAnywhere Enterprise
Installation Guide
This completes the installation and launch DeviceAnywhere Studio. A DeviceAnywhere Studio
shortcut
7
is placed on your desktop.
Enter your login credentials. These credentials are authenticated against the Access Server IP/port
information entered when you configured your installation. DeviceAnywhere Studio remembers the
last used profile for subsequent logins.
NOTE You can always change/edit profile information.
a
In the login dialog box, click Show advanced.
b
Click the Change button next to Active profile.
You can edit profile information in the dialog box that appears.
4.9.3 Installing DeviceAnywhere Studio on Mac OS X
To install DeviceAnywhere Studio on Mac OS X:
1
Ensure that you have JDK v1.5+ on your client machine.
2
Copy DeviceAnywhereStudio.dmg from the distribution medium/site.
3
Drag the DeviceAnywhere Studio icon into the Application folder on your desktop.
4
Double-click DeviceAnywhere Studio in your Application folder to launch the program.
5
Enter your credentials and select Login.
4.10
Mobile Devices
In order to control device input and view device output in the DeviceAnywhere Studio client application,
you must the device to your Ensemble Server and associate it with a device package. Adding a new
device to a DeviceAnywhere Enterprise environment involves:
64
Keynote Confidential
Installation Guide
1
DeviceAnywhere Enterprise
Attaching, or onboarding, a device to an Ensemble Server—The onboarding process is run from
DeviceAnywhere Studio and requires a device profile XML file provided by Keynote. Each XML file
contains important device-related information that is essential to using the device in
DeviceAnywhere Studio. If you do not have the XML file for any of your devices, contact your
Keynote Solutions Consultant.
The onboarding process is documented in the platform-specific smartphone setup guides available
on the documentation web page.
2
Assigning the device to a package(s)
3
Assigning the package to user group(s)
4
Verifying the device
4.10.1 Provisioning Packages with Devices
When a device has been onboarded, it can be selected and assigned to packages using tools in the
DeviceAnywhere Enterprise Portal. By default, imported devices are assigned to the All Devices package.
NOTE Only a user with the Account Admin role can add and provision packages in the DeviceAnywhere
Portal.
To provision a package with devices:
1
Log in to the DeviceAnywhere Portal.
2
Select the Device Management link.
3
Select the Packages tab.
4
Click the Edit link next to the package you wish to provision. This displays the list of devices
available in the Not provisioned pane at screen left.
Keynote Confidential
65
DeviceAnywhere Enterprise
Installation Guide
5
Select a device from the list and click the right arrow
(Already provisioned).
to move it to the list of provisioned devices
6
Repeat this step to select your devices.
7
Save your changes. The Portal displays a message that the package has been updated.
This feature allows you to group devices into packages and for assigning to different user groups. Having
multiple packages allows you to assign only those devices that are relevant to a specific set of users.
4.10.2 Assigning Packages to User Groups
NOTE Only a user with the Account Admin role can assign packages to user groups in the
DeviceAnywhere Portal.
To assign a package:
1
Log in to the DeviceAnywhere Portal.
2
Select the User Management link.
3
From the User Groups section, click Edit next to the user group you wish to assign a package to.
4
In the Packages section, select a package from the Restricted pane and click the right arrow
move it to the list of Allowed packages.
66
Keynote Confidential
to
Installation Guide
DeviceAnywhere Enterprise
5
Repeat this step to assign as many packages as you wish to the group.
6
Save your changes. The Portal displays a message that the user group has been updated.
4.10.3 Verifying Device Installation
You must install and launch DeviceAnywhere Studio to verify devices. Log in to DeviceAnywhere Studio.
You should see provisioned devices appear online. You should be able to right-click and acquire any
device to begin interacting with it.
Keynote Confidential
67
DeviceAnywhere Enterprise
5
Installation Guide
System Verification
This section provides a few test scenarios to validate your DeviceAnywhere test environment.
5.1
Restarting the Access Server
Restarting the Access Server restarts all the software components in the DeviceAnywhere installation. On
occasion, some DeviceAnywhere components might not restart automatically. As DeviceAnywhere
software servers run as a service, you can restart them from the Services menu.
The Access Server can be restarted as follows:
1
Select Start > Run.
2
Type services.msc in the command window and press Enter.
NOTE You can also access services by selecting Start > Control Panel > Administrative Tools >
Services.
3
Select the MC AccessServer service.
4
Select Restart.
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 the build date and
database information clearly displayed (see the highlighted area in the image below).
68
Keynote Confidential
Installation Guide
DeviceAnywhere Enterprise
Figure 5-1 Access Server Log
5.2
Verifying DeviceAnywhere Functionality
This section lists functional tests to exercise DeviceAnywhere core functions. If you can perform these
tests without generating an error message, then the DeviceAnywhere test environment should be
considered successfully installed.
Table 5-1 DeviceAnywhere Core Functionalities Verification
#
Test Name
Description
Expected Result
1
Studio login test
Log in to DeviceAnywhere Studio with
correct credentials.
Verify that DeviceAnywhere Studio
is launched successfully.
2
Device lock/unlock
Select a package and lock/unlock any
device.
Device is acquired and released
successfully.
3
Key press
Click a few keys on the device to verify
that it accepts input.
The device accepts inputs and the
screen updates to reflect the inputs.
4
LCD test
Navigate the device applications to test
that the LCD display is properly
updated.
The LCD screen on the device is
displayed clearly in
DeviceAnywhere Studio.
5
Create action/state/test
case (for Test
Automation Customers)
In the Test Automation view, create an
action, state, and test case. Execute the
action and the test case and upload the
results. Check results in the Portal.
Action and test case are executed
successfully and results are
uploaded to the Portal.
6
DeviceAnywhere Portal
configuration in
DeviceAnywhere
Studio/Access Server
Check Portal configuration in
DeviceAnywhere Studio and the Access
Server.
Verify that the Portal is configured
properly in DeviceAnywhere Studio
and Access Server by uploading the
test case execution result.
Keynote Confidential
69
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertising