Creating your own Web shares

Applies to the following products: 
Questionmark Perception
Applies to the following Perception versions: 
Perception 5.2
Perception 5.1

When you run the Perception Server install application, the default web shares required by Perception Server will be automatically created. However, users are provided with the option to not create the web shares automatically so that they can be created and configured manually if required.

To create the web shares manually, you will need to create some virtual web directories that are assigned to sub-directories of the Perception installation folder. These directories can then be shared to provide entry points to Perception. For example, if your web site URL is example.com you might want to access perception.php as follows:

http://example.com/assessments/perception.php

For this web entry point to function, you must tell the web server that the web share name (virtual directory name) /assessments maps onto the directory in which you have installed QPLA in to.

The following table outlines the default web shares and their access requirements.

Default physical directory Default web share name HTTP Access needed
C:\Program Files\Questionmark\Perception5\QABS\ qabs Read and Scripts
C:\Program Files\Questionmark\Perception5\EM\ em5

Read and Scripts

Enable parent paths must be on, please refer to Configuring Parent Paths permissions

C:\Program Files\Questionmark\Perception5\QPLA\runtime\ perception5 Read
C:\Program Files\Questionmark\Perception5\OpenAuthoring\ OpenAuthoring Read and Scripts
C:\Perception5\Repositories\Shared\<repository name>\PLMS\packages plms5 Read and Scripts
C:\Program Files\Questionmark\Perception5\QMWISe\ qmwise5 Read and Scripts
C:\Program Files\Questionmark\Perception5\EM\dotnetcore\repXCL4\ repxcl5 Read and Scripts
C:\Program Files\Questionmark\Perception5\ST\ QMSCTWeb Read and Scripts
C:\Perception5\Repositories\Shared\<repository name>\content <repository name>_con Read
C:\Perception5\Repositories\Shared\<repository name>\resources <repository name>_res Read
C:\Perception5\Repositories\Shared\<repository name>\system <repository name>_sys Read
C:\Perception5\Repositories\Shared\<repository name>\togo <repository name>_togo Read and Scripts

You can create your own web shares, naming them as required. However, the virtual directories will need to be directed to the physical directories highlighted in the table and be assigned the necessary access permissions.

To create the web shares manually in IIS 6, complete the steps below:

  1. In IIS Manager, expand the local computer, expand the Default Web Site folder, right-click the site or folder within which you want to create the virtual directory, point to New, and then click Virtual Directory. The Virtual Directory Creation Wizard appears.
  2. Click Next
  3. In the Alias text-box, type a name for the virtual directory (Choose a short name that is easy to type because the user types this name.)
  4. Click Next
  5. In the Path box, type or browse to the physical directory in which the virtual directory resides, and then click Next
  6. Under Allow the following permissions, select the check boxes for the access permissions you want to assign to your users (as indicated in table above), and then click Next
  7. Click Finish. The virtual directory is created below the currently selected folder level

To create the web shares manually in IIS 7, complete the steps below:

  1. Open IIS Manager
  2. In the Connections pane, expand the Sites node in the tree, and then click to select Default Web Site.
  3. In the Actions pane, click View Applications
  4. On the Applications page, in the Actions pane, click Add Application
  5. In the Add Application dialog box, type a name in the Alias text-box. This alias is used to access the content from a URL.
  6. In the Physical path text box, type the physical path of the content folder, or click Browse to navigate through the file system to find the folder.
  7. Select the Application user (pass-thru authentication) option in the Connect As dialog box.
  8. Click Test Settings to verify the settings that you specified for the virtual application
  9. Click OK