Install a Local Version of SQL Server 2008 Or Oracle 11G

Copyright © 1998-2013 Questionmark Computing Ltd. All rights reserved. Questionmark and Perception are either registered trademarks or trademarks of Questionmark Computing Ltd in the United States of America and the United Kingdom and other countries. Microsoft and Windows are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. Other product and company names mentioned herein might be trademarks of their respective owners. Other product and company names mentioned herein might be trademarks of their respective owners. VERSION 2.2

Table of Contents

Notes about this install guide ...... 9 What's new in Perception 5.4? ...... 9 How is this guide organized? ...... 9 Who is the audience for this install guide? ...... 10 Security information ...... 10 Perception's architecture ...... 11 System requirements ...... 13 Recommended hardware...... 13 Disk space required ...... 14 Supported operating systems ...... 14 Supported database systems ...... 15 Supported browsers ...... 17 Software prerequisites ...... 17 License files...... 17 Virtual environments ...... 17 Creating a single-server Perception installation ...... 19 What does a single-server installation mean? ...... 19 The installation process (Get started!) ...... 19 1. Install a server OS ...... 21 2. Install and configure the prerequisites ...... 22 3. Configure PHP ...... 28 4. Install the prerequisites on your ETL server ...... 31 5. Install a database system to handle the ETL_Temp database ...... 34 6. Install the ETL service on your ETL server ...... 37 7. Configure AppFabric ...... 39 8. Creating the shared repository database on your database server ...... 43 Create a Tablespace and User ...... 47 Setting up a Local Service Name ...... 50 9. Create an ODBC connection to your shared repository database ...... 53 10. Download and install Perception ...... 56

11. Create the Main and Results Warehouse (RW) databases ...... 62 12. Create the temporary ETL (ETL_temp) database...... 70 13. Configure the environment ...... 74 14. Create the shared repository ...... 76 15. Create the database links ...... 84 16. Migrate settings from your Perception server to your ETL server ...... 87 17. Launch Enterprise Manager and start the ETL service ...... 88 Creating a load-balanced Perception installation ...... 90 What does load balancing Perception mean? ...... 90 System requirements ...... 91 The installation process (Get started!) ...... 92 1. Creating the shared repository database on your database server ...... 94 Create a Tablespace and User ...... 98 Setting up a Local Service Name ...... 101 2. Create your first Perception server ...... 104 2a. Install a server OS ...... 105 2b. Install and configure the prerequisites ...... 106 2c. Configure PHP ...... 112 2d. Install a database system to handle the ETL_Temp database...... 115 2e. Configure AppFabric ...... 118 2f. Create an ODBC connection to the shared repository database ...... 122 2g. Download and install Perception ...... 125 2h. Create the Main and Results Warehouse (RW) databases ...... 131 2i. Create the temporary ETL (ETL_temp) database ...... 139 2j. Configure the environment ...... 143 2k. Create the shared repository ...... 145 2l. Creating database links ...... 153 2m. Migrating settings from your Perception server to your ETL server ...... 156 2m. Launch Enterprise Manager and start the ETL service ...... 157 3. Set up your file shares ...... 159 4. Configure the ServerSettings.config file ...... 160 5. Update the web.config files ...... 161 6. Configure IIS 7 ...... 162

7. Configure the license ...... 163 8. Update the Enterprise Manager settings ...... 164 9. Export server configuration to your 2nd/3rd/... Perception server ...... 165 10. Create a second (and third/fourth/...) Perception server ...... 166 11. Copy across settings from Server 1 to other servers ...... 167 12. Setting stickiness and affinity ...... 168 13. Testing your load-balanced environment ...... 169 Creating a multi-tiered (custom) Perception environment ...... 170 What does a multi-tiered (custom) installation mean? ...... 170 The installation process (Get started!) ...... 171 Further custom installation options ...... 172 1. Create the shared repository database on your database server ...... 175 Create a Tablespace and User ...... 179 Setting up a Local Service Name ...... 182 2. Install an OS on your Assessment Delivery Web Server (QPLA) server .... 185 3. Install the prerequisites on your Assessment Delivery Web Server (QPLA) server 186 4. Configure PHP on your Assessment Delivery Web Server (QPLA) server .. 189 5. Install Assessment Delivery Web Server ...... 192 6. Install an OS on your ETL Services Server server ...... 196 7. Install the prerequisites on your ETL Services Server server ...... 197 8. Install a database system to handle the ETL_Temp database ...... 200 9. Install ETL Services Server ...... 202 10. Install an OS on your Perception Application Server server ...... 204 11. Install the prerequisites on your Perception Application Server server .. 205 12. Configure AppFabric ...... 211 13. Create an ODBC connection to your shared repository database ...... 216 14. Install Perception Application Server ...... 219 15. Create the Main and Results Warehouse (RW) databases ...... 224 16. Create the temporary ETL (Temp_ETL) database ...... 232 17. Configure the environment ...... 236 18. Create the shared repository ...... 238 19. Create the database links ...... 246

20. Migrating settings from the Perception Application Server to the ETL Services Server ...... 249 21. Launch Enterprise Manager and start the ETL service ...... 250 Setting up File Upload questions in a multi-tiered installation ...... 253 On the Assessment Delivery Web Server...... 253 On the Perception Application Server...... 258 Updating the File Upload folder setting...... 262 Setting up firewall rules for a multi-tiered installation ...... 263 Upgrading from a previous version of Perception ...... 264 Recommendations for installing from a version of Windows that can't be upgraded . 265 Recommendations for installing from a version of Windows that can be upgraded ... 265 Upgrading from Perception 3 ...... 267 Upgrading from Perception 4 ...... 268 Copying the Perception 4 files and folders to your new server ...... 268 Setting up the ODBC connection on your new server ...... 269 Installing Perception ...... 269 Configuring the databases and reconnecting/upgrading your shared repository ...... 270 Upgrading from Perception 5.1 or 5.2 ...... 276 Create a backup ...... 276 Install the prerequisites ...... 276 Install a local version of SQL Server 2008 or Oracle 11g ...... 277 Install Perception ...... 277 Configure the databases and reconnect/upgrade your shared repository ...... 279 Upgrading from Perception 5.1 or 5.2 to a new server ...... 285 Copy the Perception 5 files and folders to your new server ...... 285 Set up the ODBC connection on your new server ...... 286 Install Perception ...... 286 Configure the databases and reconnect/upgrade your shared repository ...... 287 Advanced information ...... 293 ADV1. Licensing Perception ...... 294 Download a new or extended evaluation license file ...... 294 Manually retrieve a license ...... 295 Automatically activate your license ...... 297

Manually activate a license file ...... 298 ADV2. Language packs ...... 303 Installing language packs for Windows Server 2008 and R2 ...... 303 ADV3. Running from behind a firewall ...... 304 ADV4. Folder permissions for Perception ...... 307 ADV5. Create the virtual directories manually ...... 311 ADV6. Configure Perception to use SSL ...... 314 ADV7. Restrict access to Perception ...... 317 AVD8. Uninstall Perception ...... 319 ADV9. Additional scalability recommendations for high-volume installations320 Assessment block and question block caching ...... 320 ASP.Net configuration ...... 321 FastCGI ...... 321 Oracle configuration ...... 321 Participant and QABS affinity ...... 322 Expensive features that should be avoided in high-volume scenarios ...... 322 ADV10. Using a non-English version of Windows Server 2008...... 323 Appendix ...... 324 A1. Create the databases manually ...... 325 A2. Manually link the databases ...... 332 A3. Configure the SMTP service ...... 334 A4. Illegal characters ...... 339 A5. Troubleshooting ...... 340 A6. Installation checklist ...... 341 A7. Security ...... 344 General recommendations ...... 344 Phishing ...... 344 Request validation in ASP.NET ...... 344 Connecting to Authoring Manager ...... 344

Welcome! Questionmark Perception 5.4 allows assessments to be delivered online, offline, via Learning Management Systems, and through Test Centers. Click on the section below that matches the kind of Perception environment you want to create for installation instructions: Get started on a single-server install!

Get started on a load-balanced install!

Get started on a multi-tiered (custom) install! If you are looking for information about installing Perception 5.1 or 5.2, please refer to the following installation guide instead: Questionmark Perception 5.1 and 5.2 Install Guide For further information on the contents of this install guide and the general Perception installation process, please refer to: Notes on this install guide

Notes about this install guide

Questionmark Perception 5.4 is an enterprise-level assessment management system and, as such, includes all the complexities of installing and maintaining as most other enterprise systems. If your organization does not have sufficiently qualified database and system administrators, please consider using the Certified Installation solution available from Questionmark. This service can be made available for:  Installation of Questionmark Perception  Installation of connectors for integration of Questionmark Perception with other systems For more information, please refer to: Questionmark Consulting Services

This page includes the following sections:  What's new in Perception 5.4?  How is this guide organized?  Who is the audience for this install guide?  Security information

What's new in Perception 5.4?

For information about what is new in Perception 5.4, please refer to the following Knowledge Base article for details: What's new in Questionmark Perception 5.4? For a list of known issues with Perception 5.4, please refer to the following Knowledge Base article for details: What are the known issues with Questionmark Perception 5.4?

How is this guide organized?

This guide is organized into several sections and is designed to provide information on how to:  Create a single-server of Perception environment  Create a load-balanced installation of Perception environment  Create a multi-tiered installation of Perception environment  Upgrade from Perception 5.1 and 5.2  Upgrade from a previous version of Perception (like Perception 4 or Perception 3) To view the recommended information for each of the above scenarios, please view the corresponding section in the left-hand table of contents.

Who is the audience for this install guide?

This guide provides you with the information necessary to install Questionmark Perception 5.4 in your organization's IT environment. It is designed for IT specialists and application administrators and expects that the people carrying out the tasks described in this guide are familiar with the concepts of installation and configuration of server software applications.

Security information

For information on various aspects of the security of Perception and actions you can take to ensure it is secure, please refer to the following section of this guide:  A7. Security

Perception's architecture

Questionmark Perception 5.4 contains a zone-based architecture. This architecture means that each zone contains a specific application that, when configured to work together, form the Perception application. How the zones work can be defined by an organization to create a deployment architecture suitable for its needs. With the flexible nature of Perception, this can be a number of different options. Perception is designed to be tiered and scalable. The deployment architectures are:

Type Description

Single server This setup is made of three separate servers. One application server (where Perception is installed), one database server, and one ETL server.

Load balanced When it comes to load balancing, you have the option of load balancing Perception in both the single-server and multi-tiered configurations. Load-balancing provides a way of dealing with a high load while providing fail-over reliability for high stakes requirements.

Multi tiered This configuration can include 4+ servers, where various parts of Perception are installed on separate servers to increase throughput of specific component(s).

The diagram below shows the possible configurations (click the image to enlarge it):

In addition to the new architecture, there are several new databases required to store data from each zone, as well as the shared repository database that has existed in previous versions of Perception. The databases required are shown in the diagram below, where:  Shared repository is the shared repository database as found in previous versions of Perception. This database contains the user, questions, assessments, and result data. This database is referred to as Perception_REPO in this guide. However, if you are upgrading from a previous version, this will be the name of your existing shared repository database.  Perception_MAIN contains administrative user data and is used to store configuration information for all the servers in the Perception installation  Perception_RW is the Results Warehouse, which (temporarily) contains the result data taken from the shared repository by way of the ETL service. The data stored in the Result Warehouse is used to form the various Analytics reports that exist.  ETL_Temp is the temporary ETL database used by the Extract, Transform, and Load (ETL) service and needs to be installed on the same machine as the ETL service. The ETL service retrieves data from the Shared Repository database, and, while it is transformed into meaningful data for Question Analytics, it is temporarily stored in this database before being loaded into the Results Warehouse.

When creating the Perception databases, as outlined, for instance, in step 11 and step 12 of single-server install, it is important to note that the databases must be separate databases with unique names. The configuration application assumes the databases will be unique and that none will be used more than once (i.e., it assumes that the Perception_MAIN database will not also be used as the shared repository).

System requirements

Before you install Perception, you should ensure that your system(s) meets the minimum requirements. These are listed in the following sections:  Recommended hardware  Disk space required  Supported operating systems  Supported database systems  Supported browsers  Software prerequisites  License files  Virtual environments Note that you will need administrative permissions for the server on which you will be installing Perception.

The name(s) of the server that you install Perception on and your database servers must not contain any underscores, dashes, or other illegal characters, or the database links will not be created when it comes time to configure Perception. For more information on illegal characters and Questionmark, please refer to A4. Illegal characters.

Recommended hardware

The recommended hardware for Perception 5.4 will depend on the environment you intend to install it in. For details about the recommended hardware requirements for Perception, please refer to the Question Perception Scalability Guide.

The recommended hardware specifications for your Perception server are:  An x86- or x64-compatible (not ia64) quad-core CPU, preferably of the i7 or Xeon (E3, E7, or Sequence) processor family  8GB RAM (At least 4GB RAM at minimum)  SAS or SATA 7200RPM HDD or greater

The recommended hardware specifications for your ETL server are:  An x86- or x64-compatible (not ia64) quad-core CPU, preferably of the i7 or Xeon (E3, E7, or Sequence) processor family  At least 4GB RAM (8GB RAM recommended)  SAS or SATA 7200RPM HDD or greater

The recommended hardware specifications for your database server(s) depends on the load that your database server(s) will need to accommodate; a higher volume of assessments being delivered will require more computing power or you will see degraded performance. As with the recommendations for the Perception and ETL servers, for more details about scalability and recommended hardware requirements, you can refer to the Scalability Guide linked to above, but it is recommended that the hardware of your database server(s) is at least as powerful as what is recommended for the Perception and ETL servers.

As Perception can be hardware-intensive at times (especially when delivering a large number of

assessments at once), it is recommended that the server you install Perception on is dedicated solely to running Perception. Try to keep your Perception server as free of other programs as possible for maximum performance. If you have other applications or web services, install them on different servers.

Disk space required

Depending on the type of installation you intend to set up, the server on which you want to install Perception must have the required free disk space as highlighted in the following table:

Install type Free disk space required

Perception software prerequisites/PHP 50MB

Single-server install Approximately 2GB

Multi-tiered install ...on server hosting QPLA: 200MB

...on server hosting Enterprise Manager: Less than 1GB

...on server hosting Analytics: Less than 1GB

Additional space will be required to store logs, resources, and database files that are created or required by Perception.

Supported operating systems

Perception is compatible with the following English-language operating systems:  Microsoft Windows Server 2008 (x86 and x64)  Microsoft Windows Server 2008 R2 (x64) Non-English versions of Windows Server 2008 are not supported. While they might work with Perception after some modifications, please be aware that doing so is at your own risk.

Although unsupported by Questionmark, if you are using a non-English version of Windows Server

2008 (or R2), please refer to the ADV10. Using a non-English version of Windows Server 2008 for information on some settings that must be edited for the ETL service to function correctly.

If you want to create assessments that use non-English characters, you will need to install the correct language pack(s). This is to ensure that non-English characters can be displayed by Perception and the database server(s) used. For further information about installing language packs, please refer to ADV2. Language packs.

Supported database systems

The following database systems and versions can be used with Perception. If you will be using Perception for production use, Perception should be installed on an application server (or multiple servers) and the Perception databases should be installed on a separate database server.

SQL Server

For the shared repository (Perception_REPO), Main (Perception_MAIN), Results Warehouse (Perception_RW), and temporary ETL (ETL_Temp) databases, you can use:  SQL Server 2008  SQL Server 2008 R2 You can use either the 32- or 64-bit version of SQL Server 2008.

Please note that the database servers should have a minimum of 4GB RAM.

Installation notes

In SQL Server, there are two database collations to set, the SQL Server collation and the Database collation. For English and non-English characters to appear correctly when using SQL Server, your collations should be set as:  SQL Server collation must be configured to use the SQL_Latin1_General_Cp1_CI_AS collation. This collation utilizes the 1252 (ANSI - Latin 1) codepage. The SQL_Latin1_General_Cp1_CI_AS collation is the case-insensitive version. You should take care not to use the case-sensitive version of the collation. The case-sensitive version can be identified with the initials CS appearing in the collation title while the case insensitive version can be identified by the initials CI. This collation must be set when installing SQL Server. Please be aware that when installing SQL Server 2008, it will automatically attempt to get the most-appropriate collation depending on what the server locale has been set as. In most cases, this will need to be manually changed to use the SQL_Latin1_General_Cp1_CI_AS collation.  Database collation must be set to SQL_Latin1_General_Cp1_CI_AS to ensure that all data written in Perception is stored and displayed correctly. It will be set to this collation by Perception when it is installed.

Please note that the collation used should be SQL_Latin1_General_Cp1_CI_AS, not

Latin1_General_CI_AS.

Users wishing to set up the English version of Perception on a non-English operating system should ensure that the correct language packs are installed for both the database and the operating system. Additionally, the language pack 1252 (ANSI - Latin 1) must be installed for both servers and the SQL Server collation and database collation set to SQL_Latin1_General_Cp1_CI_AS. The question searching facility in Authoring Manager requires the full-text indexing component of SQL Server to be installed and configured and will not work without it. Once full-text indexing is installed, it will need to be enabled for the database before the repository is created.

Oracle

For the shared repository (Perception_REPO), Main (Perception_MAIN), Results Warehouse (Perception_RW), and the temporary ETL (ETL_Temp) database, you can use:  Oracle 11g R1  Oracle 11g R2 You can use either the 32- or 64-bit version of Oracle 11g for the shared repository, Main, and Results Warehouse databases. However, you must use a 32-bit version of the Oracle client on your ETL server for the temporary ETL database.

While you can use either 32- or 64-bit versions of Oracle 11g for the Perception databases on your database server, the ETL service only works with 32-bit Oracle client drivers. Even if you are running Windows Server 2008 64-bit or Windows Server 2008 R2 (which is a 64-bit operating system) on your ETL server, you will still need to install and use a 32-bit Oracle client on your ETL server (or whatever server you install the ETL service on) that is compatible with your Oracle database.

Installation notes

There are a number of factors that need to be taken in to account if using Oracle as your database system for Perception. These include:  For non-English characters (Latin characters and other Western European characters) to appear properly when using Oracle, your Oracle installation must be configured to utilize the AL32UTF8 character set  For 2-bit characters (such as Japanese or Chinese), you must utilize the WE8MSWIN125 database character set  If using the WE8MSWIN1252 database character set on a non-English operating system, the National Character Set (NLS) must be set to English (either US or UK) No other character sets can be reliably supported at this time. You can either change your database to use the appropriate character set (providing that other applications using Oracle can work with this), or else set up a separate Oracle installation with the appropriate character set for Perception to use. To use the Scoring Tool component of Perception Server with Oracle, ODP.NET (Oracle Data Provider) version 9.2 or higher must be installed on each application server you will be running Perception on. ODP.NET can be obtained from the Oracle Web site: www.oracle.com The question-searching facility in Authoring Manager requires Oracle Text to be installed and configured and will not work without it. Oracle Text is not installed by default in some versions and may need to be installed.

Other things to keep in mind when installing and configuring Oracle

 If you haven't already setup a destination file for your Oracle databases, please refer to the Set the Oracle database file destination section of the instructions in 8. Create the shared repository database on your database server.

Please note you will need to install at least 2 database instances. One will be on the database

server containing the shared repository, Perception_MAIN, and Perception_RW databases, and the other (for the ETL_Temp database) will need to be on the server running the Extract, Transform, and Load service.

Supported browsers

For information about the supported web browsers for Enterprise Manager and the Questionmark portal, please refer to the following Knowledge Base article:  What browsers does Questionmark support? Software prerequisites

The applications required by Perception are listed below:  Internet Information Services (IIS) 7 or 7.5  .NET 2.0  .NET 3.5  .NET 4.0  ASP.NET MVC 2  Microsoft Chart Controls for Microsoft .NET Framework 3.5  PHP 5.3  Windows Server AppFabric  SQL Server 2008 or Oracle 11g (for the ETL service) Optional:  SMTP For more information on each of the programs, as well as installation instructions, please refer to: 2. Install and configure the prerequisites (for a single-server install) 2b. Install and configure the prerequisites (for a load-balanced install) For a multi-tiered install, refer to steps 3, 7, and 11.

License files

When you install Perception, a license is included that allows you to use the product for 30 days. After this evaluation period expires, you will need to obtain a valid license. Please refer to ADV1. Licensing Perception for more information after you have installed Perception. Virtual environments

Perception can be installed and run in virtual environments. Questionmark supports installations of Perception in the following virtual environment platforms:

VMWare

VMWare is a virtualization solution produced by VMWare Inc. and is the market leader in virtualization. VMware software provides a completely virtualized set of hardware to the guest operating system.

Hyper-V

Hyper-V is a hypervisor-based virtualization system for 64-bit systems. It is a new virtualization technology that Microsoft implemented in Windows Server 2008 and directly replaces Microsoft Virtual Server. Hyper-V is built in to the host and guest operating systems and allows for improved performance over Microsoft's traditional virtualization methods. If using virtual environments care should be taken to ensure that the host computer running the virtualization software is robust and powerful to ensure that Perception is not left without the ability to create and store data or process actions. The virtual environments need to be setup to work as hardware based machines and should be setup with adequate amounts of memory, hard drive space and processor speed. The network configuration for the virtual environment will depend on your organization network setup, but Perception has been tested extensively using a bridged network connection from the virtual environment to the physical network.

Questionmark Perception is multi-threaded, but it is not specifically vSMP aware. It will use

whatever resources the guest operating system makes available to it. While it can be run on guest operating systems that utilize a single vCPU or multiple vCPUs, it is unable to communicate directly with the host operating system in a virtualized environment to optimize resources via vSMP. The workload of delivering assessments from Perception is handled by IIS. IIS assigns a response to a thread and thus the processor use is determined by IIS and not by Perception. General virtualization tips include:  Don't mix single vCPU and multiple vCPU guests on a single host  Prevent the straddling of CPUs (For example, a server with 2x 6-core CPUs cannot run 3x 4- vCPU guests efficiently, as one would straddle two CPUs.)  Ensure host capacity is capable of supporting all guest operating systems under load. If the host constantly runs at close to 100%, consider separating some of the guest systems to other hosts.

Creating a single-server Perception installation

This page includes the following sections:  What does a single-server installation mean?  The installation process (Get started!)

What does a single-server installation mean?

It is important to note that the following order of steps is just one possible suggestion that you can follow to set up a single-server installation of Perception. Although this section includes a specific order of installation steps, it is possible to follow a different order as you set up your Perception environment, as your configuration may differ depending on your needs and look different from the one outlined here.

This section of the install guide provides instructions specifically for a single-server installation, meaning that your "single-server" environment will include three servers in total (we're using the term "single- server" because there is only a single Perception server in this configuration):  Perception server o Perception 5.4 will be installed on this server o Perception's software prerequisites will be installed on this server  ETL server o The ETL service and the temporary ETL (ETL_Temp) database will be installed on this server  Database server o The database system (SQL Server or Oracle) you will be using will be installed on this server o The shared repository (Perception_REPO), Main (Perception_Main), and Results Warehouse (Perception_RW) databases will be installed on this server The installation process (Get started!)

The installation process for a single-server Perception environment is as follows: 1. Install a server OS on your Perception server 2. Install and configure the prerequisites on your Perception server 3. Configure PHP on your Perception server 4. Install the prerequisites on your ETL server 5. Install a database system to handle the ETL_Temp database on your ETL server 6. Install the ETL service on your ETL server 7. Configure AppFabric on your Perception 8. Create the shared repository database on your database server 9. Create an ODBC connection to your shared repository database on your Perception server 10. Install Perception on your Perception server

11. Create the Main and Results Warehouse (RW) databases 12. Create the temporary ETL (ETL_Temp) database on your ETL server 13. Configure the environment 14. Create the shared repository 15. Create the database links 16. Migrating settings from your Perception server to your ETL server 17. Launch Enterprise Manager and start the ETL service

1. Install a server OS

Before you begin to install and configure Questionmark Perception, you need to install an operating system on the server on which you intend to install Perception. Questionmark Perception is compatible with the following operating systems:  Microsoft Windows Server 2008 (x86 and x64)  Microsoft Windows Server 2008 R2 (x64)

Recommended hardware

The recommended hardware specifications for Perception 5.4 depend on the environment in which you intend to install it. For details about recommended hardware specifications, please refer to the Questionmark Perception Scalability Guide. The recommended hardware specifications for the server on which you plan on installing Perception are:  An x86- or x64-compatible (not ia64) quad-core CPU, preferably of the i7 or Xeon (E3, E7, or Sequence) processor family  8GB RAM (4GB RAM at minimum)  SAS or SATA 7200RPM HDD or greater  Approximately 3GB of storage space Older processors will run Perception, but please note the performance of Perception is directly related to processor speed. Additional storage space will be required to store logs, resources, and database files that are created or required by Perception.

2. Install and configure the prerequisites

Once you have installed your server operating system, the following applications are required to be installed on the same server on which you intend to install Perception. These programs must be installed and configured before you install Perception. Click on the individual program to see instructions and notes on its installation and configuration. Alternatively, you can use the Web Platform Installer to download and automatically install most of the prerequisites at once, instead of downloading and installing each application individually.

Required applications  Internet Information Services (IIS) 7 or 7.5 Windows Server 2008 and R2 use IIS 7 and 7.5 respectively. The process of installing them is very similar. You will need to ensure that you have administrative user rights on the server on which you plan to install IIS. To install IIS: 1. Click Start | All Programs | Administrative Tools | Server Manager 2. In the Server Manager window, scroll down to Roles Summary, and then click Add Roles. The Add Roles Wizard will start with a Before You Begin page. The wizard asks for verification of the following:  The administrator account has a strong password  The network settings, such as IP addresses, are configured  The latest security updates from Windows Update are installed 3. Select Web Server (IIS) on the Select Server Roles page. An introductory page will open with links for further information. 4. Select the IIS services to be installed on the Select Role Services page. Add the following modules, and click Next:  Static Content  Default Document  ASP  ASP.NET  .NET Extensibility  CGI  ISAPI Extensions  ISAPI Filters  Windows Authentication  IP and Domain Restrictions  IIS Management Console  IIS Management Scripts and Tools  IIS 6 Management Components (or the whole IIS 6 Management Compatibility subtree) If you are using the 32-bit version of Windows Server 2008, you should also include the following:  HTTP Redirection  Request Filtering

5. Click Add Required Role Services 6. Wait for IIS to complete installing, and click Finish 7. Locate the Features Summary, and click Add Features 8. Enable the following Features:  .NET Framework 3.0 (inside the .NET Framework 3.0 Features category)  HTTP Activation (inside the WCF Activation category) 9. Click Next, followed by Install 10. Once the features have been installed, click Close and exit Server Manager Once IIS is enabled, make sure the ASP.NET State Service is running. To do this: 1. Click Start | Administration Tools | Services 2. Locate and right click on the ASP State Service entry 3. Click Properties 4. Make sure the Startup type is set to Automatic 5. Click Start to start the service now 6. Click OK and exit out of the Services window

Running 32-bit applications in 64-bit IIS If you are planning to run 32-bit applications (i.e., Perception) in a 64-bit version of IIS (on a 64- bit version of Windows Server 2008), you will need to ensure that the correct settings are enabled. The settings are enabled by running specific commands and parameters from the command line. You will need to launch the command line prompt as an administrative user (you can do this by logging in as an administrative user or by right-clicking on the command prompt icon and clicking Run as administrator). To enable 32-bit applications to run in 64-bit IIS, enter the following command at the prompt: cscript %SYSTEMDRIVE%\inetpub\adminscripts\adsutil.vbs SET W3SVC/AppPools/Enable32bitAppOnWin64 1 To enable the 32-bit version of the .NET 2.0 Framework for use with Perception, you will need to run the following command:

%SYSTEMROOT%\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis.exe -i ...or, if that is unavailable, try:

%SYSTEMROOT%\Microsoft.NET\Framework64\v2.0.50727\aspnet_regiis.exe -i  .NET 2.0 SP2 In Windows Server 2008, the .NET 2.0 Framework is installed by default. No further action is required.  .NET 3.5 + SP1 The .NET Framework 3.5 is not available by default on Windows Server 2008 (32- or 64-bit). However, it is already installed on Windows Server 2008 R2, but it needs to be enabled. If you are using Windows Server 2008 (32- or 64-bit) you can download it from: Microsoft .NET Framework 3.5 Service Pack 1 www.microsoft.com/downloads/en/details.aspx?FamilyID=ab99342f-5d1a-413d-8319- 81da479ab0d7

To enable the .NET Framework 3.5 on Windows Server 2008 R2: 1. Click Start | Administrative Tools | Server Manager 2. Select Features 3. Click Add Feature 4. Place a check in the .NET Framework 3.5.1 Features check-box 5. Click Add Required Feature 6. Click Next followed by Install 7. Once it has finished installing, click Close

If you are using Windows Server 2008 (32-bit), you will also need to enable HTTP Activation. To do this: 1. Navigate to Start | Programs | Administrative Tools | Server Manager 2. Select Features, and click Add Features 3. In the Add Features dialog, under .NET Framework 3.0 Features under WCF Activation, select HTTP Activation 4. Click the Next to install Once setup, you will need to enable the WCF portion of the .NET Framework 3.5. To do this: 1. Launch the command line 2. Navigate to:

C:\WINDOWS\Microsoft.NET\Framework\v3.0\Windows Communication Foundation\ Or, the following, if you are using a 64-bit operating system: C:\WINDOWS\Microsoft.NET\Framework64\v3.0\Windows Communication Foundation\ 3. Enter the following and press Enter:

You can download Microsoft Chart Controls for Microsoft .NET Framework 3.5 from: Microsoft Chart Controls for Microsoft .NET Framework 3.5 To download and install: 1. Navigate to the above site 2. Download MSChart.exe 3. Once downloaded, double-click on the file to launch the installer 4. Accept the end user license agreement and allow the program to install 5. Click Finish to close the installer  PHP 5.3 and PHP Manager for IIS You can download PHP 5.3 from: PHP 5.3.16 You can download PHP Manager for IIS from: PHP Manager for IIS If you download the prerequisites with the Web Platform Installer, PHP Manager will be installed automatically and no further configuration is necessary. Once you have installed PHP and PHP Manager, you will need to make sure that PHP is configured appropriately for Perception. This will be discussed later in this guide in step 3 (Configure PHP).  Windows Server AppFabric You can download Windows Server AppFabric from: Windows Server AppFabric The version of AppFabric required is dependent on the version of Windows Server 2008 you are using.

Windows Version AppFabric Version

Windows Server 2008 (32-bit) 6.0 (x86)

Windows Server 2008 (64-bit) 6.0 (x64)

Windows Server 2008 R2 6.1 (x64)

For complete instructions about how to install AppFabric, please refer to the following: Windows Server AppFabric installation and configuration guide If you are using Windows Server 2008 (32- or 64-bit), you will be required to install the Windows Management Framework successfully before installing Windows Server AppFabric. If you have installed all the latest Windows updates, this should already be installed. However, for further details, please refer to: Windows Management Framework (Windows PowerShell 2.0, WinRM 2.0, and BITS 4.0) To install AppFabric: 1. Double-click the file you downloaded

2. Click Yes to accept the terms and conditions, followed by Next 3. Select you preferences for the Customer Experience, Help Improve, and Critical Updates options, and click Next 4. Select the following features and click Next (uncheck the other options so that only the following features are selected)  Runtime Features (automatically checked when the option below is checked)  Caching Services  Administration Tools (automatically checked when the option below is checked)  Cache Administration

5. Click Install to start the installation process Once AppFabric is installed, you will be asked if you want to configure it. For the time being, uncheck the checkbox and exit the installer. Once you have finished installing all the requisites, you will need to come back and configure AppFabric. Configuring AppFabric for Perception will be discussed later in this guide in step 7 (Configure AppFabric). Optional applications  SMTP Perception can be configured to send emails to participants at the end of assessments or with Email Broadcast. If you do not want to configure Perception to send emails, however, this is not required.

It is possible to configure Perception to send emails using a local SMTP service in IIS or connect to an external SMTP service (for example, one that is provided by your internet service provider). To find out more about installing and configuring SMTP, please refer to: A3. Configure the SMTP service Use the Web Platform Installer to download and install the required prerequisites Microsoft's Web Platform Installer makes it easy to download most of the necessary prerequisites for Perception in one place and install them automatically. The Web Platform Installer will download and all of the software required by Perception that does not have to be installed manually. Microsoft Web Platform Installer 4.5 can be downloaded from: Microsoft Web Platform Installer 4.5 The following programs must be installed manually, using the installation instructions in the above section (i.e., they are not included in the Web Platform Installer):  Microsoft Chart Control for Microsoft .NET Framework 3.5  Internet Information Services (IIS) 7 or 7.5  Windows Server AppFabric Click one of the following link to launch the Web Platform Installer and download and install the prerequisites:  Install the prerequisites [view URL1]

1 http://www.microsoft.com/web/gallery/install.aspx?appsxml=&appid=NETFramework4;NETFramework35 ;NETFramework20SP2;MVC2;PHP53;PHPManager

3. Configure PHP

Once you have installed the software prerequisites that Perception requires, you will need to configure PHP 5.3 (or higher) so that it works with Perception and at peak performance. You will need to:

Enable the relevant PHP extensions

In some instances, if FastCGI has not been enabled, you will not be able to enable or disable

extensions. For instructions on how to enable FastCGI, please refer to the following: Enable FastCGI Support in IIS 7 on Windows Server 2008, Windows Server 2008 R2, Windows Vista, or Windows 7

1. Launch Internet Information Services (IIS) Manager (not Internet Information Services (IIS) 6.0 Manager) 2. Select your server from the Connections list on the left 3. In the Features View pane, locate and double-click PHP Manager 4. Under PHP Extensions, click Enable or disable an extension 5. Ensure that the following extensions are enabled:  CURL (php_curl.dll)  SOAP (php_soap.dll)  XSL (php_xsl.dll)  OpenSSL, if planning to run Perception using SSL via HTTPS (php_openssl.dll) 6. To enable an extension: a. Select it from the disabled list b. Click Enable from the Actions pane

Configure the FastCGI instances

If FastCGI has not been enabled on your server, please refer to the following for instructions on

how to enable it: Enable FastCGI Support in IIS 7 on Windows Server 2008, Windows Server 2008 R2, Windows Vista, or Windows 7

Now, you will need to carry out some configuration changes to ensure that PHP is tuned for use with Perception. To do this: 1. Launch IIS Manager 2. Select your server from the Connections list on the left 3. In the Features View pane, locate and double-click FastCGI Settings 4. Select the PHP entry, and click Edit... from the Actions pane

5. Ensure that the Instance MaxRequests setting is set to 10000 6. The Max Instances setting needs to be set to 10 times the number of processors you have on the server. For example, if your server has 2 processors, the Max Instances would be 20. If you server has 4 processors, the Max Instances should be 40.

7. Click OK PHP has now been configured and is ready to use.

After you have enabled the relevant extensions and configured the FastCGI instances, continue on to step 4 using the link below.

4. Install the prerequisites on your ETL server

The following applications need to be installed on your ETL server. These programs must be installed and configured before you install the ETL service. Click on the individual program to see instructions and notes on its installation and configuration. Alternatively, you can use the Web Platform Installer to download and automatically install most of the prerequisites at once, instead of downloading and installing each application individually. These programs must be installed and configured before you install the ETL Services Server. Click on the individual program to see instructions and notes on its installation and configuration. Alternatively, you can use the Web Platform Installer to download and automatically install most of the prerequisites at once, instead of downloading and installing each application individually. Programs marked (manual) must be downloaded and installed manually and cannot be downloaded via the Web Platform Installer. Details for configuring SQL Server can be found on the following page, step 5 (Install a database system to handle the ETL_Temp database on your ETL server).

Required applications

 Microsoft .NET Framework 4.0 You can download .NET 4.0 from: Microsoft .NET Framework 4.0 Once downloaded, double-click on the installer and follow the instructions to install .NET 4.  Internet Information Services (IIS) 7 or 7.5 (manual) Windows Server 2008 and R2 use IIS 7 and 7.5 respectively. The process of installing them is very similar. You will need to ensure that you have administrative user rights on the server on which you plan to install IIS. To install IIS: 1. Click Start | All Programs | Administrative Tools | Server Manager 2. In the Server Manager window, scroll down to Roles Summary, and then click Add Roles. The Add Roles Wizard will start with a Before You Begin page. The wizard asks for verification of the following:  The administrator account has a strong password  The network settings, such as IP addresses, are configured  The latest security updates from Windows Update are installed 3. Select Web Server (IIS) on the Select Server Roles page. An introductory page will open with links for further information. 4. Select the IIS services to be installed on the Select Role Services page. Add the following modules, and click Next:  Static Content  Default Document  ASP

 ASP.NET  .NET Extensibility  CGI  ISAPI Extensions  ISAPI Filters  Windows Authentication  IP and Domain Restrictions  IIS Management Console  IIS Management Scripts and Tools  IIS 6 Management Components (or the whole IIS 6 Management Compatibility subtree) If you are using the 32-bit version of Windows Server 2008, you should also include the following:  HTTP Redirection  Request Filtering 5. Click Add Required Role Services 6. Wait for IIS to complete installing, and click Finish 7. Locate the Features Summary, and click Add Features 8. Enable the following Features:  .NET Framework 3.0 (inside the .NET Framework 3.0 Features category)  HTTP Activation (inside the WCF Activation category) 9. Click Next, followed by Install 10. Once the features have been installed, click Close and exit Server Manager Once IIS is enabled, make sure the ASP.NET State Service is running. To do this: 1. Click Start | Administration Tools | Services 2. Locate and right click on the ASP State Service entry 3. Click Properties 4. Make sure the Startup type is set to Automatic 5. Click Start to start the service now 6. Click OK and exit out of the Services window

%SYSTEMROOT%\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis.exe -i ...or, if that is unavailable, try:

%SYSTEMROOT%\Microsoft.NET\Framework64\v2.0.50727\aspnet_regiis.exe -i  SQL Server 2008 or Oracle 11g (manual)

Install the prerequisites [view URL2]

2 http://www.microsoft.com/web/gallery/install.aspx?appsxml=&appid=NETFramework4;NETFramework35 ;NETFramework20SP2

5. Install a database system to handle the ETL_Temp database

Your ETL server needs to have the following prerequisites installed (apart from a database system):  Microsoft .NET Framework 4.0  Internet Information Services (IIS) 7 or 7.5 (manual) You can install .NET 4.0 manually or automatically, using the appropriate Web Platform Installer link below. IIS must be installed manually.  Install the prerequisites [view URL3]

A database system for the ETL_Temp database needs to be installed on your ETL server. A database is needed on the same server where the ETL service is installed to hold result data while it is being readied for the Results Warehouse. Because your Extract, Transform, and Load service is on a different server from the database, it becomes more efficient to ETL the data to a local database and then move it to the destination database in the correct format. This is illustrated in the diagram below:

For instructions on how to install either SQL Server 2008 (or 2008 R2) or Oracle 11g, please refer to the accompanying documentation of each database system. Once you have installed the database system you will be using for the ETL service, see the appropriate section below to configure your database system for use with Perception.

SQL Server 2008

3 http://www.microsoft.com/web/gallery/install.aspx?appsxml=&appid=NETFramework4;NETFramework35 ;NETFramework20SP2;

Enable TCP/IP

The following network options that are disabled by default will need to be enabled. 1. From the Start menu, navigate to Programs | Microsoft SQL Server 2008 | Configuration Tools | SQL Server Configuration Manager 2. Expand SQL Server Network Configuration, and select Protocols 3. Enable TCP/IP and Named Pipes 4. Close the SQL Server Configuration Manager

Start SQL Browser

1. From the Start menu, navigate to Programs | Microsoft SQL Server 2008 | Configuration Tools | SQL Server Configuration Manager 2. Click SQL Server Services in the left-hand pane, or double-click SQL Server Services in the right-hand pane 3. Start SQL Server Browser

Add Firewall exceptions

If you have a software firewall installed on your server, you will need to add exceptions for the SQL Server and SQL Browser services. If you are using Windows Firewall, do the following: 1. From the Start menu, navigate to Control Panel | Windows Firewall 2. Click Allow a program through Windows Firewall 3. Go to the Exceptions tab 4. Click Add Program 5. Browse to and select C:\Program Files\Microsoft SQL Server\MSSQL10.\MSSQL\Binn\sqlserver.exe or C:\Program Files (x86)\Microsoft SQL Server\MSSQL10_50.\MSSQL\Binn\sqlservr.exe if you installed the 32-bit version of SQL Server 2008 on a 64-bit operating system (the folder locations may be slightly different for your installation) 6. Click OK 7. Click Add Program 8. Browse to and select C:\Program Files\Microsoft SQL Server\90\Shared\sqlbrowser.exe or C:\Program Files (x86)\Microsoft SQL Server\90\Shared\sqlbrowser.exe 9. Click OK and then click OK again If you are using a third-party software firewall, you will need to follow their instructions to add exceptions for sqlservr.exe and sqlbrowser.exe. After you have configured SQL Server, continue to step 6 using the link below.

Oracle 11g

The 32-bit Oracle client must be used with the ETL service and temporary ETL database, even if you are using a 64-bit version of Windows Server 2008. The 64-bit Oracle client will not work with the ETL service and temporary ETL database.

The 32-bit version of Oracle 11 or 11g R2 can be downloaded from the following location: http://www.oracle.com/technetwork/database/enterprise-edition/downloads/index.html Follow the relevant Oracle instructions to install Oracle 11g. For instructions about how to download and install Oracle 11g R2 manually, please refer to the documentation that accompanies the software. After you have installed Oracle, continue to step 6 using the link below.

6. Install the ETL service on your ETL server

Once you have installed the prerequisites (including a database system) on your ETL server, you can install the ETL service on this server. Copy the installer to that server and follow the steps below.

The ETL service will be installed on your ETL server.

By default, users do not have administrative user rights if you are logged on as a user other than

the built-in administrator. This is also true even if you were added to the local Administrators group on the computer (this is a new security feature in Windows Server 2008 called Local User Administrator). If you do not have these privileges, Perception will not install correctly. Log in as the built-in administrator account, or explicitly invoke applications as the built-in administrator by using the Run as administrator command. You will need to make sure you are logged in as an administrator when completing the installation of Perception.

To install the ETL Services Server: 1. Launch the installer as an administrative user (see above for details), entering the password when prompted 2. Select Custom from the Setup Type window 3. Click Next 4. Select the ETL Services Server option

5. Click Next

6. Choose where you would like to install Perception and the application data, including repository files (please note that the Repository files folder will not actually be created on this server, as it is only needed on the Business Logic tier)

You can keep the default locations or click Browse to indicate an alternative path. 7. Click Next 8. Click Install

If you are using Oracle as your database system and plan on installing the ETL service on a

different server from the temporary ETL database, there are a few things you must do to ensure that the ETL service and the ETL temporary database can communicate with each other as well as the rest of Perception. To split up the ETL service and the ETL temporary database on different servers (Oracle only): 1. Install the ETL service on the server you desire as usual, following the instructions above. 2. The server which you install the ETL service on must have SQL*Loader (sqlldr.exe) installed. To install SQL*Loader to this server, use the Oracle Universal Installer and install Oracle Database Utilities through the custom installation option. 3. Ensure that all the tnsnames.ora files are identical among hosts and point to the same Oracle instances, as well as are aware of all Oracle connections in order for database links to function 4. Continue with your multi-tiered installation and configuration of Perception be following the link below.

< Back to step 5 Continue to step 7 >

7. Configure AppFabric

Once you have installed a database for the ETL_Temp database, you need to configure AppFabric. AppFabric works by creating a distributed cache that is shared by the various servers that need it. This can speed up access to frequently accessed information such as session data. To configure AppFabric, you will need to:

Allow access to AppFabric through the Firewall AppFabric is installed as a service. The AppFabric service needs to be granted permission to send data through the firewall. This can be done in Windows Server 2008 by modifying the In and Outbound Rules. To modify the rules:

Create a UNC shared folder to place the caching details To create a UNC folder share: 1. Create a folder on your server. Choose a convenient location and name. 2. Right-click on the folder, and select Properties from Windows Explorer 3. Select the Sharing tab 4. Click Share 5. The File Sharing window displays. Add the user Network Service or a local user if you are not connected to a domain. If you are setting up a load-balanced environment, ensure each node has the same username/password. 6. Set the Permissions Level as Contributor (Read/Write on Windows Server 2008 R2) 7. Click Share, followed by Close Configure AppFabric using the AppFabric configuration wizard The following settings need to be configured on the server hosting Enterprise Manager in this single-server installation (i.e. your Perception server). To configure the caching service: 1. Click Start | Windows Server AppFabric | Configure AppFabric 2. On the Before you begin page, click Next 3. On the Configure Hosting Services page, click Next (Perception does not use hosting services) 4. On the Configure Caching Services screen, enable the Set Caching Services configuration check-box 5. Set a Caching Service account. If your computer is part of a domain, you cannot change the Caching Service account from the default of "Network Service." If your computer is part of a workgroup, you must change the Caching Service account from "Network Service" and use a local account. If you are using a local account, do not use an account with administrator privileges. The local account used for the Caching Service account only needs permissions to generate security audits (granted explicitly by adding the account to the policy in the Local Security Policy dialog box) and the right to bypass traverse checking (granted through membership in the Everyone group). 6. From the Caching Service configuration provider drop-down box, select XML

7. In the File share text-box, enter the UNC address for the folder you created above. This will be in the format \\ 8. Select New cluster 9. Select the appropriate value from the Cluster size drop-down box. The value you select will be determined by the number of computers you are going to have in your cluster, which in turn is dependant on which components are installed. Questionmark recommends that you set this to Small Cluster (1-5) unless you are installing a load-balanced system with over 5 machines.

10. Click Next 11. Make sure you have defined the appropriate ports for AppFabric. You will need to use the default ports for Questionmark Perception.

Cache port: 22233

Cluster port: 22234

Arbitration port: 22235

Replication port: 22236

The Cache port needs to be accessible by the application and the other AppFabric servers, if more than one.

The Cluster port, Arbitration port, and Replication port need to be open between the AppFabric servers, if more than one. 12. Click Next, followed by Finish Setup the cache To setup the required cache, we will use PowerShell. To do this using PowerShell: 1. On the Start Menu, click All Programs, Windows Server AppFabric, and then click Caching Administration Windows PowerShell

Please note you have to start PowerShell as an administrative user. If you are not already logged in as an administrator, right-click the PowerShell icon and select Run as administrator.

2. We will not be using the security system provided by AppFabric. Instead we will be using the Perception equivalent, so you will need to enter the following command: Set-CacheClusterSecurity -SecurityMode None -ProtectionLevel None

If you receive an error when running the Set-CacheClusterSecurity command, stop the cache

cluster and then try again by entering the following before trying step 2 again:

Stop-CacheCluster

3. Now create a new cache by entering the following command: New-Cache questionmark

Please note that the cache name is case sensitive and must be called questionmark. 3. Now you need to start the cache by entering the following command: Start-CacheCluster

Starting the cache after a server reboot Every time you restart your Perception server, you will need to restart the cache on each computer. It is recommended that you do this through PowerShell by following the steps below: 1. Click Start | Windows Server AppFabric | Cache Administration PowerShell Console 2. Enter the following:

Start-CacheCluster

If you are using SQL Server as your cache configuration provider, you can also change the Startup Type in Services for AppFabric to Automatic, although it can take ten to fifteen minutes for AppFabric to restart after a reboot through this method. If you are using XML as your cache configuration provider or the delayed start is not acceptable for your purposes, you can use a PowerShell script and a scheduled Windows task to start AppFabric automatically. See the Knowledge Base article How can I automatically start the Windows Server AppFabric Caching Service? for instructions on how to do this.

After you have completed the above steps, continue on to step 8 using the link below.

8. Creating the shared repository database on your database server

As you are installing a new instance of Perception, you now need to create a database for your shared repository. The shared repository database needs to be created on your database server.

The full version of SQL Server 2008 (or 2008 R2) or Oracle 11g must be used for the shared

repository, Perception_MAIN, and Perception_RW databases.

Select the database system that you are using on your database server and follow the instructions:

SQL Server 2008

Before you create the shared repository database In SQL Server, there are two database collations you need to set: the SQL Server collation and the Database collation. For English and non-English characters to appear correctly when using SQL Server, your collations should be set as:  SQL Server collation must be configured to use the collation SQL_Latin1_General_Cp1_CI_AS. The collation utilizes the 1252 (ANSI - Latin 1) codepage. The collation SQL_Latin1_General_Cp1_CI_AS is the case-insensitive version. You should take care not to use the case-sensitive version of the collation, which can be identified with the initials CS appearing in the collation title, while the case-insensitive version can be identified by the initials CI.

This must be applied to the instance of SQL Server when installing SQL Server. Please be aware that, when installing SQL Server 2008, it will automatically attempt to get the most appropriate collation depending on what the server locale has been set as. In most cases, this will need to be manually changed to use the SQL_Latin1_General_Cp1_CI_AS collation.  Database collation must be set as SQL_Latin1_General_Cp1_CI_AS to ensure that all data written in Perception is stored and displayed correctly. It will be set to this collation by Perception when it is created.

Please note that the collation used should be SQL_Latin1_General_Cp1_CI_AS, not

Latin1_General_CI_AS.

Users wishing to set up an English language version of Perception on a non-English operating system and database should ensure that the correct language packs are installed for both the database and the operating system. Additionally, the language pack 1252 (ANSI - Latin 1) must

be installed for both servers and the SQL Server collation and database collation set to SQL_Latin1_General_Cp1_CI_AS. The question searching facility in Authoring Manager requires the full-text indexing component of SQL Server to be installed and configured and will not work without it. Once full-text indexing is installed, it will need to be enabled for the database before the repository is created.

Create a database and user for the shared repository To create a SQL Server 2008 database for use with Perception: 1. Open SQL Server Management Studio 2. Right-click the Database folder on the attached database server and select New database 3. Enter the database name. For example, Perception_REPO. 4. From the Options page set the collation to SQL_Latin1_General_CP1_CI_AS and click OK Once you have created your database, you need to set up a new login. To do so: 1. Still in SQL Server Management Studio 2. Expand the server folder for the server on which you have created your database in the navigation pane 3. Expand the Security sub-folder 4. Right-click Logins and select New login... 5. Enter a name for the new login. For example, Perception_REPO. 6. Select SQL Server Authentication and enter a password 7. Uncheck the Enforce password expiration and User must change password at next login checkboxes 8. In the Default database list, select the database you created above. For example, Perception_REPO. 9. Open the User Mapping page and tick the database you created 10. Enable the db_owner and public permission checkboxes 11. Navigate to the Server Roles page 12. Enable the bulkadmin and public server role checkboxes

13. Click OK

Switch on full-text indexing for the shared repository database If you intend to use question searching in Authoring Manager, you will need to ensure that full-text indexing is enabled for the shared repository database. To enable full-text indexing in SQL Server Management Studio: 1. Right-click on the shared repository database (Perception_REPO), and select Properties 2. Click Files from the Select a page menu 3. Enable the Use Full-text indexing checkbox 4. Click OK

If the checkbox is already ticked and grayed out, this is because full-text indexing has been

enabled for the whole server, meaning all the databases have full-text indexing enabled by default.

Now that you have created a user and database for the shared repository, you will need to create an ODBC connection to it on your Perception server. For information about how to do this, please continue to step 9 using the link below.

Oracle

Before you create the shared repository database There are a number of factors that need to be taken in to account if using Oracle as your database server for Perception. These include:  For non-English characters (Latin characters and other Western European characters) to appear properly when using Oracle, your Oracle installation must be configured to utilize

the AL32UTF8 character set  For 2-bit characters (such as Japanese or Chinese), you must utilize the WE8MSWIN125 database character set  If using the WE8MSWIN1252 database character set on a non-English operating system the National Character Set (NLS) must be set to English (either US or UK) No other character sets can be reliably supported at this time. You can either change your database to use the appropriate character set (providing that other applications using Oracle can work with this), or else set up a separate Oracle installation with the appropriate character set for Perception to use. To use the Scoring Tool component of Perception with Oracle, ODP.NET (Oracle Data Provider) 9.2 or higher must be installed on the server on which you plan on running Perception on. ODP.NET can be obtained from the Oracle website: www.oracle.com The question searching facility in Authoring Manager requires Oracle Text to be installed and configured, and it will not work without it. Oracle Text is not installed by default in some versions and may need to be installed.

Please note:

 If you haven't already setup a destination file for your Oracle databases, please refer to the upcoming Set the Oracle database file destination section of this page.

Set the Oracle database file destination Before creating any Oracle Tablespaces, it is recommended that you ensure the database file destination path is set for your Oracle instance, especially if you are working with a new installation of Oracle.. This will need to be done on your database server used in your Perception installation before creating any Tablespaces.

If you have previously set the destination paths for your databases previously, please skip the

following section and continue with the install process as highlighted. For complete details about how you might setup the destination path, please refer to your Oracle documentation. For example: Creating Oracle-Managed Files in the Oracle Database Administrator's Guide

To do this, you will need to run a SQL command via the SQLPLUS command prompt. To enter the SQLPLUS command line interface, enter the following at a command line prompt: sqlplus system/@/

...where: is the password associated with the SYSTEM user is the server name for your Oracle installation (i.e., your database server) is the System ID for your Oracle server set during installation Once logged in, run the following command:

ALTER SYSTEM SET DB_CREATE_FILE_DEST=''

...where is the location that you would like the database (dbf) files to be located. For example, if your Oracle environment is on a:  Linux/Unix environment, the may be something like: /u01/app/oracle/oradata  Windows environment, the may be something like: C:\app\\\oradata\

...especially if you are working with a new installation of Oracle.

Create a Tablespace and User

For Oracle, you will need to create a Schema for use by the shared repository. This involves creating a Tablespace and User. The following section provides details about doing this. After ensuring that the database file destination path is set for your Oracle instance, to create a Tablespace for your database: 1. Open Enterprise Manager Console on your database server 2. Login to the database server you will be creating the new database on 3. Open the Server tab 4. Under Storage, click Tablespaces 5. Click Create 6. Enter a name for the new Tablespace. For example, Perception_REPO. 7. Under Datafiles, click Add

8. Enter the following information:  Enter a File Name for the datafile  Enter the location of an available File Directory (this file location must exist before this section will complete accurately)  Set the File Size to a larger number than the default 100MB for high-use systems

 Tick Automatically extend datafile when full (AUTOEXTEND) and specify a suitably high value in the Increment box 9. Click Continue to return to the Create Tablespace page, and then click OK to create the Tablespace. The new table will appear in the list of Tablespaces. To create a database user: 1. Open the Enterprise Manager Console 2. Login to the database server you will be creating the new database on 3. Open the Server tab 4. Under Security, click Users 5. Click Create

6. Enter the following information:  Enter a database user name and password  In the Default Tablespace box, enter the name of the Tablespace you created above  In the Temporary Tablespace box, enter the name of a temporary Tablespace. By default, this is TEMP.

7. Open the Roles tab, and click Edit List

8. Assign the user the following roles:  CONNECT  CTXAPP (only avaiable if OracleText is available)  RESOURCE 9. Click OK 10. Open the System Privileges tab, and click Edit List

11. Select the following System Privileges, and click OK:  CREATE SESSION  CREATE TABLE  CREATE PROCEDURE  CEATE SEQUENCE  CREATE SYNONYM  CREATE TRIGGER  CREATE VIEW

12. Click OK to create the user Next, you will need to configure the Local Service Name and then create an ODBC data source.

Setting up a Local Service Name

A Local Service Name is a way of defining a connection to a Tablespace. To configure the Local Service Name, you will need the Oracle client installed on the same server on which you intend to install Perception (NOT your database server). To configure the Local Service Name: 1. Open Oracle Net Manager on the same server on which you intend to install Perception (NOT your database server) 2. Select the Service Naming folder in Oracle Net Configuration | Local

3. Click the Create (+) button. The Net Service Name Wizard screen is displayed. 4. Enter a Net Service Name. For example, Perception_REPO (make a note of this name, as you will need to use it when you create an ODBC data source). 5. Click Next

6. Select TCP/IP (Internet Protocol) and click Next 7. Enter the Host Name and click Next. This is the name of the server that the Oracle database is installed on (i.e., your database server). If you are not using the default Port Number, you can enter the port you are using as well.

8. Enter the Service Name of the Oracle instance and click Next 9. Click Test to verify the connection 10. Click Finish. Save the changes when you close Oracle Net Manager. Now that you have created a user, Tablespace, and setup the Local Service Name for the repository, you will need to create an ODBC connection to it on your Perception server. For information about how to do this, please continue to step 9 using the link below.

< Back to step 7 Continue to step 9 >

9. Create an ODBC connection to your shared repository database

Now, you need to create an ODBC data source to link Perception to the shared repository database you created in step 6 so that the Shared Repository Service can correctly use it. The ODBC connection needs to be created on the same server on which you plan to install Perception. If you are using a 64-bit version of Windows (for example, Windows Server 2008 R2), you will need to use the 32-bit version of ODBC drivers. The sections below provide details about creating the ODBC connections for the following database systems:

SQL Server 2008 To create an ODBC data source: 1. Open the ODBC Data Source Administrator on the same server on which you plan to install Perception as an administrative user. To do so on a:  32-bit operating system, go to Control Panel, double-click Administrative Tools, and then double-click Data Sources (ODBC)  64-bit operating system, such as Windows Server 2008 R2, navigate to and launch the following ODBC driver: C:\Windows\SysWOW64\odbcad32.exe 2. Open the System DSN tab 3. Click Add... 4. Select the SQL Server driver for your SQL Server instance and click Finish 5. Enter a name for the new data source, and select the server you want to connect to (that is, the machine on which your database is installed, i.e., your database server) from the drop-down list. Make sure that you enter the actual server name and not "(local)" or "localhost." 6. Click Next 7. Ensure that With SQL Server authentication using a login ID and password entered by the user is selected

8. Enter the ID and password of the login you created for the Perception database (in step 8) and click Next 9. Enable the Change the default database to check-box and select your Perception database (i.e., Perception_REPO) from the drop-down list and click Next

10. Click Finish. Review the details of the new ODBC data source that will be created and click OK. You can click Test Data Source to check the connection. 11. Click OK to close the ODBC Data Source Administrator You can now begin to install Perception. Follow the link at the bottom of this page to continue to step 10.

Oracle 11g

Once you have created your shared repository database (Perception_REPO), you will need to create a data source. This should be done on the same server on which you plan to install Perceptioin, not your database server. To do so: 1. Open the ODBC Data Source Administrator on the same server on which you plan to install Perception as an administrative user. To do so on a:  32-bit operating system, go to Control Panel, double-click Administrative Tools, and then double-click Data Sources (ODBC)  64-bit operating system, navigate to and launch the following ODBC driver: C:\Windows\SysWOW64\odbcad32.exe 2. Open the System DSN tab 3. Click Add... 4. Select the 32-bit Oracle driver that corresponds to your Oracle installation from the list and click OK

5. Enter a name and description for the new data source in the appropriate text-boxes 6. Specify in the TNS Service Name text-box the Net Service Name of the server you want to connect to (that is, the machine on which your database is installed, i.e., your database server). This is the Net Service Name you specified in step 8. 7. Enter the name of the database user you have created in the User ID text-box. For example, Perception_REPO. 8. Click OK, and OK again to close the ODBC Data Source Administrator You can now begin to install Perception. Follow the link at the bottom of this page to continue to step 10.

10. Download and install Perception

After you have completed the previous seven steps, you can download and install Questionmark Perception. Perception needs to be installed on the server that you have installed all the prerequisites on. Click on the following sections to expand them and view instructions on downloading and installing Perception for a single-server installation. Download Perception The Questionmark Perception installer can be obtained from the Questionmark website. To download the installer: 1. Navigate to www.questionmark.com 2. Select Tryout & Downloads | Product Downloads 3. Locate the Questionmark Perception v5.4 - Server section and click Download Software 4. If you are not already logged in, you will be asked to provide your Questionmark Communities username and password 5. The application will now start to download and you should receive an email with the password necessary to run the installer Once the installer has downloaded, you can run it as required to install Perception. Install Perception A single-server installation involves installing all the components of Perception on a single server and then attaching it to a database hosted on another server. The installer will guide you through the process of installing Perception. The installer requires you to enter a password before it will install Perception Server. This password should have been sent to you by email. Please contact Questionmark if you have not received this email.

Please note: By default, users do not have administrative user rights if you are logged on as a

user other than the built-in administrator. This is also true even if you were added to the local Administrators group on the computer (this is a new security feature in Windows Server 2008 called Local User Administrator). If you do not have these privileges, Perception will not install correctly. Log in as the built-in administrator account, or explicitly invoke applications as the built- in administrator by using the Run as administrator command. You will need to make sure you are logged in as an administrator when completing the installation of Perception.

Once you have the necessary software in place and you know the details required, to install Perception: 1. Double-click the installer enter the required password 2. Click Next on the Welcome screen

3. Accept the End User License Agreement and click Next

4. Select the Typical install and click Next

5. Choose where you would like to install Perception and the application data, including repository files.

You can keep the default location, or click Browse to indicate an alternative path. Click Next to continue.

6. If this server is to be accessed externally, enter the URL for the web server by selecting User Defined and entering the domain name in the text-box. Alternatively, select This Computer if users will be using the computer name as the URL to access Perception.

If you are intending to access Perception using an IP address, you must select the User Defined

setting and enter the IP address in the text box. Failure to do so will cause certain functions in Perception to work incorrectly. For example:  File upload questions will not work correctly, preventing participants from uploading answers  Links to reports that a participant has access to will not work 7. Click Next 8. In the Installation Options screen, select if you would like:  To automatically create the necessary virtual directories and application pools  Enable the automatic Authoring Manager upgrade options

9. Click Next and click Install to begin the installation

A warning will be displayed indicating that PHP will need to be installed before the application will appear. Ensure you have completed the steps indicated in step 3 (Configure PHP), and click OK.

If you have not installed PHP yet, click OK and continue installing Perception. Once installed, carry out the steps indicated in step 3 (Configure PHP) before attempting to launch Perception. 10. Once the installation process has finished, check the Launch Questionmark Configuration Application option and click Finish to launch the configuration application in a browser window.

Continue to step 11 to begin configuring Perception, which begins with creating the Main and Results Warehouse (RW) databases.

11. Create the Main and Results Warehouse (RW) databases

Now you need to create the Main and Results Warehouse (RW) databases using the configuration application. For information about the configuration application, click on the following section to expand it. The configuration application The configuration process is responsible for linking the various parts of the application to their related database. The configuration application is designed to make configuring Analytics, Enterprise Manager, and the databases easier. Please follow the appropriate steps as defined below. The configuration application contains the following workflow:

If you exit the configuration application before completing all of the steps in the workflow, or want to return to the configuration application for any reason, you can navigate to:

http://localhost/configuration

You need to be logged on to your database server locally in order to access the configuration

application.

If you return to the configuration application, you can:  Resume the configuration (if you haven't completed it)  Redo a previous section  Start the configuration again (starting the configuration again does not delete existing databases)

The configuration application can create the Main and Results Warehouse (RW) databases for you automatically, or you can create them manually. Please choose your preferred method below: Automatic (the databases are created for you, using the credentials you provide)

When creating the Perception databases, it is important to note that the databases must be

separate databases with unique names. The configuration application assumes the databases will be unique and that none will be used more than once (i.e., it assumes that the Perception_MAIN database will not also be used as the shared repository). Also, if you don't use the default names, please ensure you do not use illegal characters when creating your database. For more information, please refer to A4. Illegal characters.

To create the Main and Results Warehouse (RW) databases automatically, you will need to provide several details. The details required will depend on what database technology you are using, but will include:  Database base administrative user details, including password  The address of the database server To create your databases automatically: 1. Make sure the Automatic option box is selected 2. Select the database type you are installing Perception on from the Choose database type drop- down list

3. Refer to the relevant section depending on your database type:  SQL Server 2008 1. Enter the fully-qualified name for the database server you want to use in the format ., e.g., db2008.myorganization.local. You may also

use an IP address, or just the server name if the server is not part of a domain. Do not use (local) or localhost. If you have multiple instances on your database, remember to include the instance name where necessary: \

2. When administering this database server, you need to login to the relevant service. Select how you connect to the database server using the I connect using drop- down list. If you login using:

 Windows Authentication - You will need to enter the Windows username and password associated with the system administrator for the database server. If you are using a domain server, remember you should use the fully qualified \. For example, myorganization\dbsysadmin.  SQL Server Authentication - You will need to enter the database system administrator and password. For example, on SQL Server 2008, you will typically use the sa user. 3. Enter a username for the database user you would like the configuration application to make. This user will be used by the ODBC connection to allow the databases to communicate with Perception.

You can allow the configuration application to create a random password for this user, or you can specify your own by unchecking the Auto Generate checkbox. 4. You can now enter the names you would like to assign to the two databases created at this time (the Perception Main database and the Analytics Results Warehouse database).

Enter the desired names for the databases. 5. Click Create. Once the databases have been setup, you will see the following:

6. Click Continue to move to the next step You can now continue to step 12 using the link below.  Oracle 11g 1. Enter the fully-qualified name for the database server you want to use in the format ., e.g., orcl11g.myorganization.local.

2. Enter the System ID (as defined when Oracle was setup) 3. Define the Port used to communicate with Oracle (as defined when Oracle was setup) 4. Enter the Username and Password details of an Oracle user who has permissions to create Users, Tablespaces, and Roles

5. From the This user should connect as drop-down box, define the role the user (entered above) has on the Oracle system. This could be:  Default - A standard user assigned these permissions  SysDba - System Database Administrator  SysOper - System Operator Each of the above users require unique commends for connecting, so please make sure that the user you entered is defined appropriately. 6. Now you need to define the names of the User and corresponding Tablespaces for the Perception Main database and the Analytics Result Warehouse database that you would like the configuration application to make.

You can assign your own User and Tablespace name, and you can choose to auto- generate the password or create your own by checking/unchecking the Auto Generate checkbox. 7. Click Create. Once the databases have been setup, you will see the following:

8. Click Continue to move to the next step You can now continue to step 12 using the link below. Manual (you create the databases manually, and then provide the details to the configuration application) To manually create the Main and Results Warehouse (RW) databases, you will need to create your databases first. For instructions on doing so, please refer to the following section: A1. Create the databases manually After you have created your databases, refer to the relevant section depending on your database type:  SQL Server 2008 1. In the configuration application, select Manual from the How do you want to create the databases? section 2. Select SQL Server from the Choose database type drop-down list

3. Enter the fully qualified name for the database server you want to use in the format ., e.g., db2008.myorganization.local. You may also use an IP address, or just the server name if the server is not part of a domain. Do not use (local) or localhost. If you have multiple instances on your database, remember to include the instance name where necessary: \ 4. Enter the Login and Password details for the user you created for the databases 5. Enter the Database name you assigned to the Perception shared repository database (Perception_MAIN) you created 6. Enter the Database name you assigned to the Result Warehouse database (Perception_RW) you created 7. Click Create Once the databases have been setup, you will see the following:

8. Click Continue You can now continue to step 12 using the link below.  Oracle 11g 1. In the configuration application, select Manual from the How do you want to create the databases? section 2. Select Oracle from the Choose database type drop-down list 3. Enter the Database server name where you created the schemas 4. Enter the SID for the Oracle server and make sure the port number is correct for your database 5. Enter the User and Tablespace and Password details for the Perception_MAIN database you manually created 6. Enter the User and Tablespace and Password details for the Perception_RW database you manually created 7. Click Create Once the databases have been setup, you will see the following screen:

8. Click Continue You can now continue to step 12 using the link below.

12. Create the temporary ETL (ETL_temp) database

Now you need to create the temporary ETL (ETL_Temp) database using the configuration application.

The ETL_Temp database needs to be created on your ETL server. The configuration application can create the ETL_Temp database for you automatically, or you can create it manually. Please choose your preferred method below: Automatic (the ETL_Temp database is created for you, using the credentials you provide) To create the ETL_Temp database automatically: 1. Select Automatic 2. Select the database type you are installing Perception on from the Choose database type drop- down list

3. Refer to the relevant section depending on your database type:  SQL Server 2008 1. Enter the database server name of your ETL server, which is where your ETL service is installed

2. Select how you connect to the database on your ETL server using the I connect using drop-down list. If you login using:  Windows authentication - You will need to enter the Windows username and password associated with the system administrator for the database server. If you are using a domain server, remember you should use the fully qualified \. For example, myorganization\dbsysadmin.  SQL Server authentication - You will need to enter the database system administrator and password. For example, on SQL Server 2008, you will typically use the sa user. 3. Enter a Database Name for the temporary ETL database. Please ensure you do not use illegal characters when naming your temporary ETL database. For more information, please refer to A4. Illegal characters. 4. Set a password or use an auto-generated one 5. Click Create. Once complete, you should be presented with a screen similar to the following:

Now you can continue on to step 13 using the link below.  Oracle 11g 1. Enter the name of your ETL server (it must be entered in uppercase form in the Enter database server name: text-box), which is where the ETL service is installed 2. Add the Oracle System ID (SID) for your ETL server (it must be entered in uppercase form) and ensure the Port used to connnect is correct 3. Enter a Username and Password for an Oracle user who has permission to create users, Tablespaces, and assign roles. For example, the username might be SYSTEM. 4. Determine how this user should connect to the Oracle instance in the This user should connect as drop-down list. For example, SysDba. 5. Enter a name for the User and Tablespace you want to create. For example, the user might be named Perception_ETL_Temp. 6. Set a password or use an auto-generated one 7. Click Create. Once complete, you should be presented with a screen similar to the following:

Please note that it is important to ensure that all tnsnames.ora files need to be aware of all

Oracle connections in order for database links to function. All tnsnames.ora files need to be identical and point to the same Oracle instances.

Now you can continue on to step 13 using the link below. Manual (you create the database manually, and then provide the details to the configuration application) To manually create the ETL_Temp database, you will need to create the database first. For instructions on doing so, please refer to the following section: A1. Create the databases manually After you have created the temporary ETL database, refer to the relevant section depending on your database type:  SQL Server 2008 1. In the configuration application, select Manual from the How do you want to create the databases? section 2. Select SQL Server from the Choose database type drop-down list 3. Enter the address of your ETL server, which is where your ETL service in installed. Enter the fully-qualified name in the format ., e.g., db2008.myorganization.local. You may also use an IP address or just the server name if the server is not part of a domain. Do not use (local) or localhost. Remember to include the instance name where necessary: \ 4. Enter the name of the temporary ETL database you created before 5. Click Create. Once complete you should be presented with a screen similar to the following:

Now you can continue on to step 13 using the link below.  Oracle 11g

1. In the configuration application, select Manual from the How do you want to create the databases? section 2. Select Oracle from the Choose database type drop-down list 3. Enter the Database server name where you created the ETL_Temp schemas (note that this will be your Perception server in this single-server installation) 4. Enter the Sytem ID (SID) for the Oracle server and make sure the Port number used to connect is correct for your database 5. Enter the User and Tablespace and Password details for the ETL_Temp database you manually created 6. Click Create. Once complete, you should be presented with a screen similar to the following:

Please note that it is important to ensure that all tnsnames.ora files need to be aware of all

Oracle connections in order for database links to function. All tnsnames.ora files need to be identical and point to the same Oracle instances.

Now you can continue on to step 13 using the link below.

13. Configure the environment

For example: http:///portal/  Service layer This component is designed to facilitate the communication of all parts of the software. The service layer is generally kept behind the firewall, so you can use the machine name (including the fully-qualified name) or the IP address of the server where the service layer is installed. You will need to enter the URL for your Perception server.

You can enter the address of the server(s) and the port used by it in the following format: :22233,:22233.

The server address can be in the form of machine name (including the fully-qualified name) or the IP address. The servers listed are separated by a comma (,). ...where my_server is the domain name of the relevant server.

To configure the environment: 1. Add the relevant information for to the Enter the portal address and Enter the service layer address text-boxes 2. Once you have entered the relevant addresses, click Continue 3. You will be shown a screen similar to the following:

4. Click Continue Now you can continue on to step 14 using the link below.

14. Create the shared repository

Now you will need to launch Shared Repository Manager and create a shared repository. Because you are installing a new copy of Perception, you will see a screen similar to the following:

If you are accessing the configuration application locally on the server, you can click Launch SRM to load the Shared Repository Manager. If you are not logged in locally, you will need to log in to your Perception server and launch the Shared Repository Manager from: Start | All Programs | Questionmark | Perception 5.4 Once the Shared Repository Manager is loaded, to create a new repository: 1. Click Add New Repository... in the Shared Repositories menu.

The Repository Creation Wizard is displayed. 2. Click Next > 3. Enter a name for your repository in the Repository name text-box 4. Select the type of database you are using from the Database type drop-down list 5. Select the language you would like your reports to appear in from the Language for standard reports drop-down and click Next >

6. Enter an Initial topic name and Initial assessment folder name and click Next >. The Initial topic name is the topic at the top of the topic hierarchy and is also called the root topic. The Initial assessment folder is the assessment folder at the top of the assessment folder hierarchy and is also called the root folder. 7. If you wish to enable security, ensure that the Check to enable security in the new repository box is ticked and click Next >. We recommend that you enable security. If you are setting up a new repository on your database, security is enabled by default and cannot be de- selected. 8. The following option will require you to fill in your database details  If you selected SQL Server or Oracle as your database type, you should see the following screen:

To continue: o Select the Database DSN (Database Source Name) of your database from the drop- down list. You must have already created a blank SQL Server or Oracle database and setup an ODBC connection to it, otherwise the DSN name will not appear in the list (refer to step 9 (Create an ODBC connection to your shared repository database) for instructions if you have not already done so). o Tick the Check to run database scripts checkbox, as this is required to create the Perception tables in your database o Tick the Check to enable question searching capability checkbox if you want authors to be able to use the Question Search feature in Authoring Manager. Ensure that OracleText has been installed if you are using an Oracle database or full-text indexing has been installed and configured for the database if you are using SQL Server. Please refer to the documentation that accompanied your database server for more information about how to install and configure the necessary options. o If you will be importing data from Perception version 3, tick Check to import from V3. Otherwise, leave the check box unchecked. If the data you will be importing from Perception version 3 contains Japanese data (characters) or similar data, place a check in the Convert V3 Japanese data on import checkbox.

If no DSN appears in the drop-down list, ensure you made an ODBC connection using the 32-bit

driver and not the 64-bit version. For further information, please refer to step 9 (Create an ODBC connection to your shared repository database).

9. Click Next > 10. You should now be presented with either of the following screens, depending on the database server you are using:

 SQL Server

You will need to enter the correct details for the SQL Server user you assigned to the database. To check you are logging into the correct database you created earlier, click Options >>.

Once the details have been entered, click OK.  Oracle

You will need to enter the correct details you assigned to the Oracle database to ensure that the ODBC connection can successfully be made (if this dialogue box does not automatically appear, you can access it by clicking the Change Login Details button).

Once the details have been entered, click OK. 11. Confirm the repository creation process by clicking Next >. The repository will be created.

12. Click Finish to close the Repository Creation Wizard. A warning screen will be displayed.

13. Click Yes to allow the shared repository to be accessed by authorized users of Enterprise Manager as well as participants

If you click No, the shared repository will not be set to be accessed by Perception Server and

Enterprise Manager and all participant-facing software will not work. You must click Yes.

The shared repository has now been created. The "Configure Perception Server" window will be displayed to allow you to configure the repository and Perception to work together. To configure the two: 1. Specify the Perception Server Application Folder. Either accept the default location, or, if you installed Perception in a different location, click Browse to specify it. 2. The Web Access box displays the default names for the Resources Web Share and Content Web Share. Either accept the default name, or enter your own.

The System Web Share is only applicable if you have installed Perception in a multi-tiered

environment. The default web share as created by the installation is MyRepository_sys. This web share allows QPLA to access the necessary files on the QABS machine in a multi-tiered environment.

3. If you will be using Questionmark to Go or QMWISe for 3rd-party applications to communicate with Perception, check the Configure this feature checkbox and update the QMWISe URL so that it points to the QMWISe web share on your Perception server. Click Test to set and test the QMWISe URL setting. 4. To configure QMWISe fully, you will also need to create a unique 8-digit Trusted Key that Perception can use to verify any communication between Perception and your 3rd-party applications. For further information about Trusted Keys and QMWISe, please refer to the QMWISe API Guide. 5. Set the Web Share you would like to use for Questionmark to Go

6. Click OK 7. A Configuration Server Notice will be displayed confirming that the configuration file has been successfully modified. Click OK to continue. 8. The repository has now been created and will appear in the Shared Repository Manager

9. Now that the repository has been created, you can continue with the process of configuring Perception by returning to your browser window and clicking Continue

10. You will be shown the following screen. In the Enter a Display Name text-box, enter a name that you would like to associate with your shared repository. It will be used by the various zones for communication.

11. Click Continue. You will be presented with a success screen and asked to continue. Now you can continue on to step 15 using the link below.

15. Create the database links

You will now be asked to create the database links. A database link is required to allow tables and views from one database be used by another. The process of linking up the databases is different for Oracle and SQL Server. Database links can be configured automatically, Where the configuration application is provided with administrator details for each database server and it runs the necessary procedure, or manually, where you create the links manually on each database server and the configuration application confirms if they are setup correctly. Please click on the relevant section below to expand its instructions: SQL Server Automatically To automatically link the database servers: 1. Select Automatically from the Would you like to setup your database links: option. You will be shown an entry for each database server used in your installation. So you could have one entry, similar to below, or you could have several entries. For each entry the Databases on the Server section will identify which database(s) can be found on the server identified in the Database Server Name. 2. When creating the links to the server, you will need to login as an administrator. Select how you connect to the database server using the I connect using drop-down list. If you login using:

Windows authentication - You will need to enter the windows username and password associated with the system administrator for the database server. If you are using a domain server, remember that you should use the fully-qualified domain name: \. For example: myorganization\dbsysadmin

SQL Server authentication - You will need to enter the database system administrator and password. For example, on SQL Server 2008 you will typically use the sa user. 3. Repeat the above steps for each database entry and click Create Now you can continue on to step 16 using the link below to finish installing Perception. Manually

For instructions about setting up you database links manually, please refer to the following before completing the steps below: A2. Manually link the databases To manually link the database servers: 1. Select Manual from the Would you like to setup your database links: option 2. Click Verify to check the linking is successful Now you can continue on to step 16 using the link below to finish installing Perception. Oracle Automatically To automatically link the database servers: 1. Select Automatically from the Would you like to setup your database links option buttons 2. Enter your database administrator username and password 3. Click Create

Now you can continue on to step 16 using the link below to finish installing Perception. Manually For instructions about setting up you database links manually, please refer to the following before completing the steps below: A2. Manually link the databases To manually link the database servers: 1. Select Manually from the Would you like to setup your database links: option 2. Click Verify to check the linking is successful

Now you can continue on to step 16 using the link below to finish installing Perception.

16. Migrate settings from your Perception server to your ETL server

After Perception has been installed and configured, you will need to copy the relevant configuration settings from your Perception server to your ETL server. This is partly automated. To do this: 1. Using Windows Explorer, navigate to C:\Program Files\Questionmark\Perception5\Configuration\ImportExport (or Program Files (x86) on a 64-bit machine) on your Perception server 2. Right-click on the export.bat file and click Run as administrator. Enter the usernames and passwords as required. The export.bat file will create a .cab file. 3. Copy the .cab file to a location accessible from your ETL server 4. Copy the .cab file you created in the previous step to C:\Program Files\Questionmark\Perception5\Configuration\ImportExport (or Program Files (x86) on a 64-bit machine) on your ETL server 5. Right-click the import.bat file and click Run as administrator. Enter the usernames and passwords as required. The keys will be imported to your ETL server. 6. Reset IIS

17. Launch Enterprise Manager and start the ETL service

Once the database links have been successfully created, you will be shown a success screen and a button that you can click to enter Enterprise Manager for the first time. The URL for Enterprise Manager will follow the format below:

http:///portal// ...where is the name of the server or domain that you entered as the portal address in step 13 (Configure the environment). ...where is the name of the shared repository you created in step 14 (Create the shared repository).

Please note: It is important to ensure that the server on which Perception is installed is added to

Trusted sites in Internet Options for Internet Explorer, otherwise the Enterprise Manager Login button might not appear on the portal landing page, as Javascript is typically only enabled for trusted sites for Internet Explorer on Windows Server 2008.

To finish the installation process, you need to start and ensure that the ETL service is running. Click the section below to expand it.

Start the ETL service

Although unsupported by Questionmark, if you are using a non-English version of Windows Server

2008 (or R2), please refer to the ADV10. Using a non-English version of Windows Server 2008 for information on some settings that must be edited for the ETL service to function correctly.

Once you have finished installing and configuring the Perception, you need to ensure that the ETL service has started. To start the ETL service: 1. Log into the machine where the ETL service is installed as an administrative user (in this single- server installation, this is your Perception server) 2. Click Start 3. In the Search for programs and files text-box, enter services.msc and press Enter on your keyboard 4. Locate the Questionmark.ETL.Scheduler.Service service 5. Right-click on it and select Properties 6. Make sure the Startup type is set to Automatic 7. Under Service status, click Start and ensure the Service status entry changes to Started

8. Click OK to close the dialog window

With the ETL service now started, result data will be: A. Extracted from your shared repository database B. Transformed in the temporary ETL database into the proper format for Questionmark Analytics C. Loaded in to the Results Warehouse database so that Analytics can access it This process will happen every 3 hours by default. If you want to change the frequency of the ETL service, please refer to the following Knowledge Base article for instructions:  How can I change the frequency of the ETL service? Congratulations, you have now installed and configured Perception! Optionally, you can also configure Perception to use SSL and restrict access to Perception, as well as register Perception. For information on further post-configuration, such as setting up Perception to run from behind a firewall or configuring the SMTP service, see the Advanced information and Appendix sections of this install guide, respectively.

Creating a load-balanced Perception installation

This page includes the following sections:  What does load balancing Perception mean?  System requirements  The installation process (Get started!) This section covers how to setup a load-balanced Perception environment, meaning that your environment will include the following:  Perception server 1 o Perception 5.4 will be installed on this server o Perception's software prerequisites will be installed on this server  Perception server 2 o Perception 5.4 will be installed on this server o Perception's software prerequisites will be installed on this server  Perception server n (Perception server 3, 4, and so on...) o Perception 5.4 will be installed on this server o Perception's software prerequisites will be installed on this server  Database server o The database system (SQL Server or Oracle) you will be using will be installed on this server o The shared repository (Perception_REPO), Main (Perception_Main), and Results Warehouse (Perception_RW) databases will be installed on this server  ETL server o The ETL service and the temporary ETL (ETL_Temp) database will be installed on this server

What does load balancing Perception mean?

It is important to note that the following order of steps is just one possible suggestion that you can follow to set up a load-balanced installation of Perception. Although this section includes a specific order of installation steps, it is possible to follow a different order as you set up your load- balanced environment. Your configuration may differ depending on your needs and look different from the one outlined here, as there are a number of different load-balanced configurations that can be set up.

In most instances, a load-balanced environment is usually created for:  Increased bandwidth  High availability  Both increased bandwidth and high availability Creating a load-balanced Perception configuration is simply a case of:  Creating two or more servers with Perception installed on them

 Ensuring that each Perception installation/server points to the same databases and folder shares/NAS to store common files A load-balanced environment will result in an environment similar to the following diagram:

If you are particularly interested in high availability, you should ensure that all the components of your load-balanced environment have high availability. This includes:  The network storage for the AppFabric caching XML file  The NAS (Network Attached Storage) used to host the server settings, repository, and other supporting files  The databases are also load-balanced and clustered appropriately System requirements

The system requirements for a load-balanced installation of Perception are the same as a single-server installation. Please refer to the System requirements section for a comprehensive description.

In addition to the standard system requirements, you will need a Network Attached Storage (NAS). In a load-balanced environment, all the load-balanced machines must be able to create, view, and access all the same support files (e.g., images used in questions, resources linked to in an assessment, and graphics used in a template). Additionally, all the load-balanced machines must be able to write to the same location (e.g., when creating log files). How this is done depends on the resources available. This can be done by:  Creating a folder share on one of the load-balanced machines and allowing the other machines to access it  Using a Network Attached Storage/file server. This is essentially the same method as above, but involves employing a dedicated machine (a NAS) that handles shared storage that may or may not be load balanced itself. Other requirements include network access for all the servers to the same network to allow communication between them. You can use either software or hardware load balancers with Perception 5.4 to distribute the load between the available servers. The steps for either type of load balancer are the same. For further details, please refer to the documentation that accompanies your load-balancing software/hardware for recommended configuration details.

The installation process (Get started!)

The installation process for a load-balanced Perception environment is as follows: 1. Create the shared repository database on your database server 2. Create your first Perception server a. Install a server OS b. Install and configure the prerequisites c. Configure PHP d. Install a database system to handle the ETL_Temp database on your ETL server e. Configure AppFabric f. Create an ODBC connection to the shared repository database g. Download and install Perception h. Create the Main and Results Warehouse (RW) databases i. Create the ETL_Temp database on your ETL server j. Configure the environment k. Create the shared repository l. Create the database links m. Migrate settings from your Perception server to your ETL server n. Launch Enterprise Manager and start the ETL service 3. Set up your file shares 4. Configure the ServerSettings.config file 5. Update the web.config files 6. Configure IIS 7 7. Configure the license 8. Update the settings in Enterprise Manager 9. Export server configuration

10. Create a second (and third/fourth/...) Perception server 11. Copy across settings from your first Perception server to the second and configure IIS 7 12. Setting stickiness and affinity 13. Testing your load-balanced environment

Start the installation process on step 1 (Created shared

repository database) >

1. Creating the shared repository database on your database server

As you are installing a new instance of Perception, you now need to create a database for your shared repository. The shared repository database needs to be created on your database server.

The full version of SQL Server 2008 (or 2008 R2) or Oracle 11g must be used for the shared

repository, Perception_MAIN, and Perception_RW databases.

Select the database system that you are using on your database server and follow the instructions:

SQL Server 2008

Please note that the collation used should be SQL_Latin1_General_Cp1_CI_AS, not

Latin1_General_CI_AS.

SQL_Latin1_General_Cp1_CI_AS. The question searching facility in Authoring Manager requires the full-text indexing component of SQL Server to be installed and configured and will not work without it. Once full-text indexing is installed, it will need to be enabled for the database before the repository is created.

13. Click OK

If the checkbox is already ticked and grayed out, this is because full-text indexing has been

enabled for the whole server, meaning all the databases have full-text indexing enabled by default.

Oracle

Please note:

 If you haven't already setup a destination file for your Oracle databases, please refer to the upcoming Set the Oracle database file destination section of this page.

If you have previously set the destination paths for your databases previously, please skip the

To do this, you will need to run a SQL command via the SQLPLUS command prompt. To enter the SQLPLUS command line interface, enter the following at a command line prompt: sqlplus system/@/

ALTER SYSTEM SET DB_CREATE_FILE_DEST=''

...especially if you are working with a new installation of Oracle.

Create a Tablespace and User

7. Open the Roles tab, and click Edit List

8. Assign the user the following roles:  CONNECT  CTXAPP (only avaiable if OracleText is available)  RESOURCE 9. Click OK 10. Open the System Privileges tab, and click Edit List

11. Select the following System Privileges, and click OK:  CREATE SESSION  CREATE TABLE  CREATE PROCEDURE  CEATE SEQUENCE  CREATE SYNONYM  CREATE TRIGGER  CREATE VIEW

12. Click OK to create the user Next, you will need to configure the Local Service Name and then create an ODBC data source.

Setting up a Local Service Name

Continue to step 2 >

2. Create your first Perception server

A load-balanced Perception environment will contain more than one instances of Perception that all connect to the same databases, thereby sharing the processing load of delivering assessments and improving performance for participants, as well as authors and administrators. To create the first Perception server in your load-balanced environment, you will need to: a. Install a server OS b. Install and configure the prerequisites c. Configure PHP d. Install a database to handle the ETL_Temp database on your ETL server e. Configure AppFabric f. Create an ODBC connection to the shared repository database g. Download and install Perception h. Create the Main and Results Warehouse (RW) databases i. Create the ETL_Temp database on your ETL server j. Configure the environment k. Create the shared repository l. Create the database links m. Launch Enterprise Manager and start the ETL service

2a. Install a server OS

Recommended hardware

The recommended hardware specifications for Perception 5.4 depend on the environment in which you intend to install it. For details about recommended hardware specifications, please refer to the Questionmark Perception Scalability Guide. The minimum hardware specifications for the server on which you plan on installing Perception are:  An x86- or x64-compatible (not ia64) quad-core CPU, preferably of the i7 or Xeon (E3, E7, or Sequence) processor family  4GB RAM  SAS or SATA 7200RPM HDD or greater  Approximately 3GB of storage space Older processors will run Perception, but please note the performance of Perception is directly related to processor speed. Additional storage space will be required to store logs, resources, and database files that are created or required by Perception.

2b. Install and configure the prerequisites

%SYSTEMROOT%\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis.exe -i ...or, if that is unavailable, try:

You can download Microsoft Chart Controls for Microsoft .NET Framework 3.5 from: Microsoft Chart Controls for Microsoft .NET Framework 3.5 To download and install: 1. Navigate to the above site 2. Download MSChart.exe 3. Once downloaded, double-click on the file to launch the installer 4. Accept the end user license agreement and allow the program to install 5. Click Finish to close the installer  PHP 5.3 and PHP Manager for IIS You can download PHP 5.3 from: PHP 5.3.16 You can download PHP Manager for IIS from: PHP Manager for IIS If you download the prerequisites with the Web Platform Installer, PHP Manager will be installed automatically and no further configuration for is necessary. Once you have installed PHP and PHP Manager, you will need to make sure that PHP is configured appropriately for Perception. This will be discussed later in this guide in step 2c (Configure PHP).  Windows Server AppFabric You can download Windows Server AppFabric from: Windows Server AppFabric The version of AppFabric required is dependent on the version of Windows Server 2008 you are using.

Windows Version AppFabric Version

Windows Server 2008 (32-bit) 6.0 (x86)

Windows Server 2008 (64-bit) 6.0 (x64)

Windows Server 2008 R2 6.1 (x64)

2. Click Yes to accept the terms and conditions, followed by Next 3. Select you preferences for the Customer Experience, Help Improve, Critical Updates, and click Next 4. Select the following features and click Next (uncheck the other options so that only the following features are selected)  Runtime Features (automatically checked when the option below is checked)  Caching Services  Administration Tools (automatically checked when the option below is checked)  Cache Administration

5. Click Install to start the installation process Once AppFabric is installed, you will be asked if you want to configure it. For the time being, uncheck the checkbox and exit the installer. Once you have finished installing all the requisites, you will need to come back and configure AppFabric. Configuring AppFabric for Perception will be discussed later in this guide in step 2e (Configure AppFabric). Optional applications  SMTP Perception can be configured to send emails to participants at the end of assessments or with Email Broadcast. If you do not want to configure Perception to send emails, however, this is not required.

It is possible to configure Perception to send emails using a local SMTP service in IIS or connect to an external SMTP service (for example, one that is provided by your internet service provider). To find out more about installing and configuring SMTP, please refer to: A3. Configure the SMTP service Use the Web Platform Installer to download and install the required prerequisites Microsoft's Web Platform Installer makes it easy to download most of the necessary prerequisites for Perception in one place and install them automatically. The Web Platform Installer will download and all of the software required by Perception that does not have to be installed manually. Microsoft Web Platform Installer 4.0 can be downloaded from: Microsoft Web Platform Installer 4.0 The following programs must be installed manually, using the installation instructions in the above section (i.e., they are not included in the Web Platform Installer):  Microsoft Chart Control for Microsoft .NET Framework 3.5  Internet Information Services (IIS) 7 or 7.5  Windows Server AppFabric Click one of the following links to launch the Web Platform Installer and download and install the prerequisites:  Install the prerequisites [view URL4]

4 http://www.microsoft.com/web/gallery/install.aspx?appsxml=&appid=NETFramework4;NETFramework35 ;NETFramework20SP2;MVC2;PHP53;PHPManager

2c. Configure PHP

Once you have installed the software prerequisites that Perception requires, you will need to configure PHP 5.3 (or higher) so that it works with Perception and at peak performance. You will need to:

Enable the relevant PHP extensions

In some instances, if FastCGI has not been enabled, you will not be able to enable or disable

extensions. For instructions on how to enable FastCGI, please refer to the following: Enable FastCGI Support in IIS 7 on Windows Server 2008, Windows Server 2008 R2, Windows Vista, or Windows 7

Configure the FastCGI instances

If FastCGI has not been enabled on your server, please refer to the following for instructions on

how to enable it: Enable FastCGI Support in IIS 7 on Windows Server 2008, Windows Server 2008 R2, Windows Vista, or Windows 7

7. Click OK PHP has now been configured and is ready to use.

After you have enabled the relevant extensions and configured the FastCGI instances, continue on to step 2d using the link below.

2d. Install a database system to handle the ETL_Temp database

A database is needed on the same server where the ETL service is installed to hold result data while it is being readied for the Results Warehouse. In a load-balanced environment, you will need to create this temporary ETL database on the same server on which you plan to install the ETL service. The reason for installing another database is that because your Extract, Transform, and Load service is on a different server from the database, it becomes more efficient to ETL the data to a local database and then move it to the destination database in the correct format. This is illustrated in the diagram below:

SQL Server 2008

Enable TCP/IP

The following network options that are disabled by default will need to be enabled.

5 http://www.microsoft.com/web/gallery/install.aspx?appsxml=&appid=NETFramework4;NETFramework35 ;NETFramework20SP2;

1. From the Start menu, navigate to Programs | Microsoft SQL Server 2008 | Configuration Tools | SQL Server Configuration Manager 2. Expand SQL Server Network Configuration, and select Protocols 3. Enable TCP/IP and Named Pipes 4. Close the SQL Server Configuration Manager

Start SQL Browser

Add Firewall exceptions

If you have a software firewall installed on your server, you will need to add exceptions for the SQL Server and SQL Browser services. If you are using Windows Firewall, do the following: 1. From the Start menu, navigate to Control Panel | Windows Firewall 2. Click Allow a program through Windows Firewall 3. Go to the Exceptions tab 4. Click Add Program 5. Browse to and select C:\Program Files\Microsoft SQL Server\MSSQL10.\MSSQL\Binn\sqlserver.exe or C:\Program Files (x86)\Microsoft SQL Server\MSSQL10_50.\MSSQL\Binn\sqlservr.exe if you installed the 32-bit version of SQL Server 2008 on a 64-bit operating system (the folder locations may be slightly different for your installation) 6. Click OK 7. Click Add Program 8. Browse to and select C:\Program Files\Microsoft SQL Server\90\Shared\sqlbrowser.exe or C:\Program Files (x86)\Microsoft SQL Server\90\Shared\sqlbrowser.exe 9. Click OK and then click OK again If you are using a third-party software firewall, you will need to follow their instructions to add exceptions for sqlservr.exe and sqlbrowser.exe. After you have installed SQL Server, continue to step 2e using the link below.

Oracle 11g

The 32-bit version of Oracle 11 or 11g R2 can be downloaded from the following location: http://www.oracle.com/technetwork/database/enterprise-edition/downloads/index.html

Follow the relevant Oracle instructions to install Oracle 11g R2. After you have installed Oracle, continue to step 2e using the link below.

2e. Configure AppFabric

Once you have installed a database for the ETL_Temp database on your ETL server, you need to configure AppFabric. AppFabric works by creating a distributed cache that is shared by the various servers that need it. This can speed up access to frequently accessed information such as session data. To configure AppFabric, you will need to:

Create a UNC shared folder to place the caching details To create a UNC folder share: 1. Create a folder on your server. Choose a convenient location and name. 2. Right-click on the folder, and select Properties from Windows Explorer 3. Select the Sharing tab 4. Click Share 5. The File Sharing window displays. Add the user Network Service or a local user if you are not connected to a domain. If you are setting up a load-balanced environment, ensure each node has the same username/password. 6. Set the Permissions Level as Contributor (Read/Write on Windows Server 2008 R2) 7. Click Share, followed by Close Configure AppFabric using the AppFabric configuration wizard Because you are setting up Perception in a load-balanced environment, you should follow the Microsoft best practices for setting up AppFabric caching. These best practices include:  Using SQL Server as the cache configuration provider rather than XML (if you are using Oracle, you must use XML as the cache configuration provider)  Setting up lead hosts (see Lead Hosts and Cluster Management (Windows Server AppFabric Caching) for more information)  Using Windows Server 2008 failover clustering (see Failover Clustering & Network Load Balancing for more information) To create a load-balanced environment, complete the steps in the sections above on Server 1 (the first node in the load-balanced setup), and then repeat the following steps on each subsequent node: 1. Click Start | Windows Server AppFabric | Configure AppFabric 2. On the Before you begin page, click Next 3. On the Configure Hosting Services page, click Next (Perception does not use hosting services)

4. On the Configure Caching Services screen, enable the Set Caching Services configuration 5. Set a Caching Service account.

If your computer is part of a domain, you cannot change the Caching Service account from the default of "Network Service." If your computer is part of a domain, you should follow the following best practices from Microsoft to configure the credentials correctly to get around this limitation (see Shared Folder-Based Cluster Configuration (Windows Server AppFabric Caching) for more information):

"To simplify long-term administration of the cluster configuration folder, do not run the cache service under the credentials of a domain user account. By using the default installation settings, you can use the domain computer accounts of the cache servers instead and avoid password maintenance.

If you create a Windows security group to manage access to the cache configuration shared folder, you set up permissions on that folder only once. For example, if the Windows security group is named ClusterACacheServers, it indicates that the cache servers have permission to become part of the cache cluster named ClusterA.

After you create the ClusterACacheServers security group, grant the domain computer accounts of the applicable cache servers membership to this group (for example,"domain\computername$"). Then grant ClusterACacheServers read and write permissions in the sharing and security settings of the cluster configuration shared folder. When this is set up, for each new server that you add to the cache cluster, add only the domain computer account of the new server to the security group."

If your computer is part of a workgroup, you must change the Caching Service account from "Network Service" and use a local account. If you are using a local account, do not use an account with administrator privileges. The local account used for the Caching Service account only needs the right to generate security audits (granted explicitly by adding the account to the policy in the Local Security Policy dialog box) and the right to bypass traverse checking (granted through membership in the Everyone group). If you are in a load-balanced environment, all the servers should be setup with the same username/password. 6. From the Caching Service configuration provider drop-down box, select XML 7. In the File share text-box, enter the UNC address for the folder you used on Server 1 8. Select Join cluster 9. Click Next 10. Make sure you have defined the appropriate ports for AppFabric

11. Click Next, followed by Finish Repeat this process for each of the servers in the load-balanced environment.

Setup the cache To setup the required cache, we will use PowerShell. To do this using PowerShell: 1. On the Start Menu, click All Programs, Windows Server AppFabric, and then click Caching Administration Windows PowerShell

Please note you have to start PowerShell as an administrative user. If you are not already logged in as an administrator, right-click the PowerShell icon and select Run as administrator. 2. We will not be using the security system provided by AppFabric. Instead we will be using the Perception equivalent, so you will need to enter the following command: Set-CacheClusterSecurity -SecurityMode None -ProtectionLevel None

If you receive an error when running the Set-CacheClusterSecurity command, stop the cache

cluster and then try again by entering the following before trying step 2 again:

Stop-CacheCluster

3. Now create a new cache by entering the following command: New-Cache questionmark

Please note that the cache name is case sensitive and must be called questionmark. 3. Now you need to start the cache by entering the following command:

Start-CacheCluster

Start-CacheCluster If you are using SQL Server as your cache configuration provider, you can also change the Startup Type in Services for AppFabric to Automatic, although it can take ten to fifteen minutes for AppFabric to restart after a reboot through this method. If you are using XML as your cache configuration provider or the delayed start is not acceptable for your purposes, you can use a PowerShell script and a scheduled Windows task to start AppFabric automatically. See the Knowledge Base article How can I automatically start the Windows Server AppFabric Caching Service? for instructions on how to do this.

After you have completed the above steps, continue on to step 2f using the link below.

2f. Create an ODBC connection to the shared repository database

Now, you need to create an ODBC data source to link Perception to the shared repository database you created in step 1 so that the Shared Repository Service can correctly use it. The ODBC connection needs to be created on the each server on which you plan to install Perception. If you are using a 64-bit version of Windows (for example, Windows Server 2008 R2), you will need to use the 32-bit version of ODBC drivers. The sections below provide details about creating the ODBC connections for the following database systems:

8. Enter the ID and password of the login you created for the Perception database (in step 1 [Creating the shared repository database on your database server]) and click Next 9. Enable the Change the default database to check-box and select your Perception database (i.e., Perception_REPO) from the drop-down list and click Next

Oracle 11g

Once you have created your shared repository database (Perception_REPO), you will need to create a data source. This should be done on the each server on which you plan to install Perceptioin, not your database server. To do so: 1. Open the ODBC Data Source Administrator on the same server on which you plan to install Perception as an administrative user. To do so on a:  32-bit operating system, go to Control Panel, double-click Administrative Tools, and then double-click Data Sources (ODBC)  64-bit operating system, navigate to and launch the following ODBC driver: C:\Windows\SysWOW64\odbcad32.exe 2. Open the System DSN tab 3. Click Add... 4. Select the 32-bit Oracle driver that corresponds to your Oracle installation from the list and click OK

5. Enter a name and description for the new data source in the appropriate text-boxes 6. Specify in the TNS Service Name text-box the Net Service Name of the server you want to connect to (that is, the machine on which your database is installed, i.e., your database server). This is the Net Service Name you specified in step 1 (Creating the shared repository database on your database server). 7. Enter the name of the database user you have created in the User ID text-box. For example, Perception_REPO. 8. Click OK, and OK again to close the ODBC Data Source Administrator You can now begin to install Perception. Follow the link at the bottom of this page to continue to step 2g.

2g. Download and install Perception

After you have completed the previous seven steps, you can download and install Questionmark Perception. Perception needs to be installed on the server that you have installed all the prerequisites on. Click on the following sections to expand them and view instructions on downloading and installing Perception. Download Perception The Questionmark Perception installer can be obtained from the Questionmark website. To download the installer: 1. Navigate to www.questionmark.com 2. Select Tryout & Downloads | Product Downloads 3. Locate the Questionmark Perception v5.4 - Server section and click Download Software 4. If you are not already logged in, you will be asked to provide your Questionmark Communities username and password 5. The application will now start to download and you should receive an email with the password necessary to run the installer Once the installer has downloaded, you can run it as required to install Perception. Install Perception A single-server installation involves installing all the components of Perception on a single server and then attaching it to a database hosted on another server. The installer will guide you through the process of installing Perception. The installer requires you to enter a password before it will install Perception Server. This password should have been sent to you by email. Please contact Questionmark if you have not received this email.

Please note: By default, users do not have administrative user rights if you are logged on as a

Once you have the necessary software in place and you know the details required, to install Perception: 1. Double-click the installer enter the required password 2. Click Next on the Welcome screen

3. Accept the End User License Agreement and click Next

4. Select the Typical install and click Next

5. Choose where you would like to install Perception and the application data, including repository files.

You can keep the default location, or click Browse to indicate an alternative path. Click Next to continue.

If you are intending to access Perception using an IP address, you must select the User Defined

9. Click Next and click Install to begin the installation

A warning will be displayed indicating that PHP will need to be installed before the application will appear. Ensure you have completed the steps indicated in step 2c (Configure PHP), and click OK.

If you have not installed PHP yet, click OK and continue installing Perception. Once installed, carry out the steps indicated in step 2c (Configure PHP) before attempting to launch Perception. 10. Once the installation process has finished, check the Launch Questionmark Configuration Application option and click Finish to launch the configuration application in a browser window.

Continue to step 2h to begin configuring Perception, which begins with creating the Main and Results Warehouse (RW) databases.

2h. Create the Main and Results Warehouse (RW) databases

If you exit the configuration application before completing all of the steps in the workflow, or want to return to the configuration application for any reason, you can navigate to:

http://localhost/configuration

You need to be logged on to your database server locally in order to access the configuration

application.

When creating the Perception databases, it is important to note that the databases must be

separate databases with unique names. The Configuration Application assumes the databases will be unique and that none will be used more than once (i.e., it assumes that the Perception_MAIN database will not also be used as the shared repository). Also, if you don't use the default names, please ensure you do not use illegal characters when creating your database. For more information, please refer to A4. Illegal characters.

2. When administering this database server, you need to login to the relevant service. Select how you connect to the database server using the I connect using drop- down list. If you login using:

Enter the desired names for the databases. 5. Click Create. Once the databases have been setup, you will see the following:

6. Click Continue to move to the next step You can now continue to step 2i using the link below.  Oracle 11g 1. Enter the fully-qualified name for the database server you want to use in the format ., e.g., orcl11g.myorganization.local.

8. Click Continue to move to the next step You can now continue to step 2i using the link below. Manual (you create the databases manually, and then provide the details to the configuration application) To manually create the Main and Results Warehouse (RW) databases, you will need to create your databases first. For instructions on doing so, please refer to the following section: A1. Create the databases manually After you have created your databases, refer to the relevant section depending on your database type:  SQL Server 2008 1. In the configuration application, select Manual from the How do you want to create the databases? section 2. Select SQL Server from the Choose database type drop-down list

8. Click Continue You can now continue to step 2i using the link below.  Oracle 11g 1. In the configuration application, select Manual from the How do you want to create the databases? section 2. Select Oracle from the Choose database type drop-down list 3. Enter the Database server name where you created the schemas 4. Enter the SID for the Oracle server and make sure the port number is correct for your database 5. Enter the User and Tablespace and Password details for the Perception_MAIN database you manually created 6. Enter the User and Tablespace and Password details for the Perception_RW database you manually created 7. Click Create Once the databases have been setup, you will see the following screen:

8. Click Continue You can now continue to step 2i using the link below.

2i. Create the temporary ETL (ETL_temp) database

Now you need to create the temporary ETL (ETL_Temp) database using the configuration application.

3. Refer to the relevant section depending on your database type:  SQL Server 2008

1. Enter the database server name of your Perception server, which is where your ETL service is installed 2. Select how you connect to the database on your Perception server using the I connect using drop-down list. If you login using:  Windows authentication - You will need to enter the Windows username and password associated with the system administrator for the database server. If you are using a domain server, remember you should use the fully qualified \. For example, myorganization\dbsysadmin.  SQL Server authentication - You will need to enter the database system administrator and password. For example, on SQL Server 2008, you will typically use the sa user. 3. Enter a Database Name for the temporary ETL database. Ensure you do not use illegal characters when creating your database. For more information, please refer to A4. Illegal characters. 4. Set a password or use an auto-generated one 5. Click Create. Once complete, you should be presented with a screen similar to the following:

Now you can continue on to step 2j using the link below.  Oracle 11g 1. Enter the name of your Perception server (it must be entered in uppercase form in the Enter database server name: text-box), which is where the ETL service and the Oracle database intended for the ETL service is installed 2. Add the Oracle System ID (SID) for your Perception server (it must be entered in uppercase form) and ensure the Port used to connnect is correct 3. Enter a Username and Password for an Oracle user who has permission to create users, Tablespaces, and assign roles. For example, the username might be SYSTEM. 4. Determine how this user should connect to the Oracle instance in the This user should connect as drop-down list. For example, SysDba. 5. Enter a name for the User and Tablespace you want to create. For example, the user might be named Perception_ETL_Temp. 6. Set a password or use an auto-generated one 7. Click Create. Once complete, you should be presented with a screen similar to the following:

Please note that it is important to ensure that all tnsnames.ora files need to be aware of all

Oracle connections in order for database links to function. All tnsnames.ora files need to be identical and point to the same Oracle instances.

Now you can continue on to step 2j using the link below. Manual (you create the database manually, and then provide the details to the configuration application) To manually create the ETL_Temp database, you will need to create the database first. For instructions on doing so, please refer to the following section: A1. Create the databases manually After you have created the temporary ETL database, refer to the relevant section depending on your database type:  SQL Server 2008 1. In the configuration application, select Manual from the How do you want to create the databases? section 2. Select SQL Server from the Choose database type drop-down list 3. Enter the address of your Perception server, which is where your ETL service in installed. Enter the fully-qualified name in the format ., e.g., db2008.myorganization.local. You may also use an IP address or just the server name if the server is not part of a domain. Do not use (local) or localhost. Remember to include the instance name where necessary: \ 4. Enter the name of the temporary ETL database you created before 5. Click Create. Once complete you should be presented with a screen similar to the following:

Now you can continue on to step 2j using the link below.  Oracle 11g

Please note that it is important to ensure that all tnsnames.ora files need to be aware of all

Oracle connections in order for database links to function. All tnsnames.ora files need to be identical and point to the same Oracle instances.

Now you can continue on to step 2j using the link below.

2j. Configure the environment

For example: http:///portal/  Service layer This component is designed to facilitate the communication of all parts of the software. You will need to enter the URL for your Perception server. The service layer is generally kept behind the firewall, so you can use the machine name (including the fully-qualified name) or the IP address of the server where the service layer is installed.

For example: http://  Windows AppFabric Server(s) Windows App Fabric is the caching service used by Perception. There may be several servers as part of your Perception installation that have AppFabric installed on them. You can enter the address of the server(s) and the port used by it in the following format: :22233,:22233. The server address can be in the form of machine name (including the fully-qualified name) or the IP address. The servers listed are separated by a comma (,). ...where my_server is the domain name of the relevant server.

4. Click Continue Now you can continue on to step 2k using the link below.

2k. Create the shared repository

Now you will need to launch Shared Repository Manager and create a shared repository. Because you are installing a new copy of Perception, you will see a screen similar to the following:

To continue: o Select the Database DSN (Database Source Name) of your database from the drop- down list. You must have already created a blank SQL Server or Oracle database and setup an ODBC connection to it, otherwise the DSN name will not appear in the list (refer to step 2f (Create an ODBC connection to your shared repository database) for instructions if you have not already done so). o Tick the Check to run database scripts checkbox, as this is required to create the Perception tables in your database o Tick the Check to enable question searching capability checkbox if you want authors to be able to use the Question Search feature in Authoring Manager. Ensure that OracleText has been installed if you are using an Oracle database or full-text indexing has been installed and configured for the database if you are using SQL Server. Please refer to the documentation that accompanied your database server for more information about how to install and configure the necessary options. o If you will be importing data from Perception version 3, tick Check to import from V3. Otherwise, leave the check box unchecked. If the data you will be importing from Perception version 3 contains Japanese data (characters) or similar data, place a check in the Convert V3 Japanese data on import checkbox.

If no DSN appears in the drop-down list, ensure you made an ODBC connection using the 32-bit

driver and not the 64-bit version. For further information, please refer to step 2f (Create an ODBC connection to your shared repository database).