Navigation Menu

Click the "+" to see inside a chapter or use the search to the right.

.

Skip to end of metadata
Go to start of metadata

 Set up prerequisites for SearchService (EDSS) and Enemy Detection (EDQSS)

 Configure automatic email notifications

 ExamDeveloper setup home page

 

Icon

The following is applicable only for ExamDeveloper version 7.1704 and above.

Icon

 

  1. Copy the self-hosted.properties file from the <SVNFolder> folder to a folder such as C:\EnvProp\, open it with a suitable text editor such as Notepad, and add/modify the following values:

     

    • LOG_ROOT_DIR=${ProgramFiles}\Pearson\logs
      This is the common folder location where all of the microservices log files will be created and stored.

    • LOG_ENV_SUBDIR=prod
      Name of the environment to be used as a suffix to the subdirectory name where the log files of individual microservices will be generated within "LOG_ROOT_DIR" (common folder that stores the microservices log files). This can be set to something like "prod" for the production instance or "beta" for the beta instance. For example, the EDRS log will be generated within a subfolder named "edrs" if the above value is left blank. This folder will be assigned the name "edrsprod" if the above value is "prod". If the value is set to "\prod", then a separate subfolder named "prod" will be created within the "edrs" subfolder, and it will contain the EDRS log file.

      For side-by-side (additional instance)

      Icon

       

      For side-by-side (additional instance) installation:
      i. Please use separate 
      self-hosted.properties and secure.properties files per instance of ExamDeveloper such as beta-self-hosted.properties and beta-secure.properties for "beta" instance.
      ii. Use unique values that are different from the values used for other existing instances of ExamDeveloper.

       

       

    • DATA_ROOT=C:\ExamDeveloperData
      This is the folder location where the application Asset folder and log files will be stored.

      For side-by-side (additional instance)

      Icon

       

      For side-by-side (additional instance) installation, please ensure that the value specified for this variable is true for the new instance of ExamDeveloper. It should not be the one meant for any other existing instances of ExamDeveloper.

       


    • EDRS_OUTPUT_DIR=C:\ExamDeveloperData\EDRSOutput
      This is the folder location where the EDRS reports get generated. 

      For side-by-side (additional instance)

      Icon

       

      For side-by-side (additional instance) installation, please ensure that the value specified for this variable is true for the new instance of ExamDeveloper. It should not be the one meant for any other existing instances of ExamDeveloper.

      Icon

      It is prudent, in the interest of data security, to encrypt the folder where EDRS stores its output. This can be done as follows:

       How to encrypt the folder where EDRS stores its output? Click to expand...
      1. Open File Explorer in Windows and right-click the folder specified in the “outputDirectory” key of the EDRS appSettings.config file and click Properties.

      2. In the folder Properties dialog, click the Advanced button.

      3. In the Advanced Attributes dialog box that appears, select the Encrypt contents to secure data option and click OK.

      4. Click OK to close the folder Properties window.

      The current contents of the selected folder are now encrypted and any files or folders that are placed into it in the future are also encrypted.


    • REPORT_SERVER_URL=http://WIN-VSGF1NBSVPB:80/ReportServer

      This is the Report Server Web Service URL shown on the Web Service URL tab of the Reporting Services Configuration Manager.

       Where is the Report Server Web Service URL? Click to learn...
      Icon

      The Report Server Web Service URL can be found by clicking the Web Service URL link on the left as shown below. If the URL is too long, some part of the URL may not be visible. In such a case, you can hover the mouse cursor over the URL and note it down from the tool tip.

    • MAIL_SENDER=examdeveloper@pearson.com
      This is the mail account on your server used to send mail from ExamDeveloper.

    • SUPPORT_EMAIL=examdeveloper@pearson.com
      This is the mail account on your server, where all the support mail sent by the clients should be received.

    • MAIL_SERVER=localhost
      This is the address of mail server, which will be used by the application.

    • MAIL_PORT=25
      This is the port of the outgoing mail server.

    • ENABLE_AUTOLOG_EMAIL=1

    • ERROR_AUTOLOG_EMAIL_ADDRESS=errorlogsreporting@pearson.com
      Please specify the email address where the error logs are to be sent.

    • APPPOOL_NAME=ExamDeveloper
      This is the name of the ExamDeveloper Application pool as shown in step 1 of IIS Web Server Configuration.

      For side-by-side (additional instance)

      Icon

       

      For side-by-side (additional instance) installation, please ensure that the value specified for this variable is true for the new instance of ExamDeveloper. It should not be the one meant for any other existing instances of ExamDeveloper.

       

       

    • WEBSITE_NAME=Default Web Site
      This is the name of the website in IIS (NOT name of the Application), "Default Web Site" in our example as seen in step 10 of IIS Web Service Configuration.

    • WEB_TARGET_DIR=C:\inetpub\wwwroot\ExamDeveloper
      This is the physical path of name of the ExamDeveloper application <ExtractedFolder> (C:\inetpub\wwwroot\ExamDeveloper\ in our example) as detailed here.

      For side-by-side (additional instance)

      Icon

       

      For side-by-side (additional instance) installation, please ensure that the value specified for this variable is true for the new instance of ExamDeveloper. It should not be the one meant for any other existing instances of ExamDeveloper.

       

       

    • APP_RELATIVE_URI_PREFIX=
      Leave it blank for a single instance installation. This is the prefix to be added to the application URI in httpClients.config files and is required for only for side-by-side (additional instance) installation, where it can be specified a value such as "beta/". While it works fine even without the "/" at the end, the App URI looks better organized with it.

    • LICENSE_SERVER=https://examdevlicense.pearsonvue.com/Server/CheckLicense.aspx
      This is the license server URL.

    • MATH_EDITOR=wiris
      This specifies that WIRIS MathML editor is going to be used. Leave this blank if using the default (FMath) MathML editor.

    • WIRIS_IMAGE_SERVICE_HOST=www.WIRISServiceHost.com/WirisServerComponent
      This specifies WIRIS image service host name if WIRIS MathML editor is going to be used as detailed here. Leave this blank if using the default (FMath) MathML editor.

    • WEB_DOMAIN=ED-HostName
      This is the host name of the server where ExamDeveloper is installed. Please ensure that you do not copy the scheme of the URL, which could be "https://" or "http://".
      For example, if the ExamDeveloper URL is https://examdev.pearsonvue.com/ExamDeveloper, then ED-HostName is examdev.pearsonvue.com, while ExamDeveloper application name is ExamDeveloper.

    • APP_DOMAIN=App-HostName
      This is the host name of the server where all the microservices are installed. Please ensure that you do not copy the scheme of the URL, which could be "https://" or "http://".
      For example, if the EDRS URL is https://examdevapp.pearsonvue.com/UniqueEDRSServiceName, then App-HostName is examdevapp.pearsonvue.com, while EDRS service name is UniqueEDRSServiceName.

       

    • WEB_RELATIVE_URI=ExamDeveloper
      This is the name of the ExamDeveloper application mentioned under Alias as detailed in step 6 of IIS Web Server Configuration.

      For side-by-side (additional instance)

      Icon

       

      For side-by-side (additional instance) installation, please ensure that the value specified for this variable is true for the new instance of ExamDeveloper. It should not be the one meant for any other existing instances of ExamDeveloper.

       

       

    • RABBIT_ADDRESS=rabbitmq://RabbitMQ-URL/ExamDeveloper
      This is the RabbitMQ virtual host address as detailed in step 1 of Create a new Virtual Host.

      For side-by-side (additional instance)

      Icon

       

      For side-by-side (additional instance) installation, please ensure that the value specified for this variable is true for the new instance of ExamDeveloper. It should not be the one meant for any other existing instances of ExamDeveloper.

    • WEB_PROTOCOL=https

      Use "https" for web application protocol to ensure secure communication.

       

    • APP_PROTOCOL=https

      Use "https" for the microservices protocol to ensure secure communication. Use "http" when not using secure communication, only for experimental purposes.


    • USE_SSL=true

      This value must be set to "true" when https is being used for the microservices (APP_PROTOCOL=https), which is recommended for secure communication. Set this value to "false" only when http is being used for microservices (APP_PROTOCOL=http), which is not recommended.

       

    • HANGFIRE_PORT=9000

      This is the value of the Hangfire port for the first instance of ExamDeveloper.
      Note: This is an optional parameter and you need to use it only if you are planning to use EDQSS.

      For side-by-side (additional instance)

      Icon

       

      For side-by-side (additional instance) installation, please ensure that the value specified for this variable is true for the new instance of ExamDeveloper. It should not be the one meant for any other existing instances of ExamDeveloper. Thus, this value should be incremented to a value such as "9001", "9002", etc.



    • REPORT_DSN_FOLDER=ExamDeveloper
      This is the name of the ExamDeveloper reporting services folder created in step 7 of Setting up Reporting Services application folder.

      For side-by-side (additional instance)

      Icon

       

      For side-by-side (additional instance) installation, please ensure that the value specified for this variable is true for the new instance of ExamDeveloper. It should not be the one meant for any other existing instances of ExamDeveloper.



    • ENABLE_TINYMCE_UPGRADE_FEATURES=false

    • ENABLE_EXAMSAVE_FEATURES=false

    • JSPELL_FOLDER=C:\Program Files (x86)\JSpell Spell Checker
      Please specify the path where the JSpell Evolution AJAX Spell Checker has been installed as seen in step 9 of the installation. Thus, if it is installed in a non-default location such as D:\JSpell Spell Checker, then the value of JSPELL_FOLDER will be D:\JSpell Spell Checker.
      You can leave the default value if JSpell Evolution AJAX Spell Checker has not been installed.

    • PROXY_SERVER_HOSTNAME=



  2. Create a file named secure.properties in a folder such as C:\SecProp\ (separate from the one containing the self-hosted.properties file as mentioned in step 1), open it with a suitable text editor such as Notepad, and add the following values:

    • LICENSE_KEY=<<Insert the license key over here>>
      This is the ExamDeveloper license key.

      For side-by-side (additional instance)

      Icon

       

      For side-by-side (additional instance) installation, please ensure that the value specified for this variable is true for the new instance of ExamDeveloper. It should not be the one meant for any other existing instances of ExamDeveloper.


    • ENCRYPTION_KEY=!#$a54?3

    • REPORT_SERVER_DOMAIN_NAME=WIN-VSGF1NBSVPB
      This specifies the domain or realm to which the username belongs. Typically, this is the host computer name where the reporting services runs or the user domain for the user configured.

    • REPORT_SERVER_USER_NAME=edReporting
      This is the administrative username used to log into the Report Manager, in step 8 of Setting up Reporting Services application folder.

    • REPORT_SERVER_PASSWORD=Password123
      This is the password for the administrative username used to log into the Report Manager, in step 8 of Setting up Reporting Services application folder.

    • MAIL_USERNAME=support
      This is the administrative username used to log into the mail server.

    • MAIL_PASSWORD=mailP@s$
      This is the password for the administrative username used to log into the mail server.


    • WEB_ADMIN_USERNAME=edisupport
      This is the default admin username to log into ExamDeveloper.

       

    • WEB_ADMIN_PASSWORD=Dummy_ED-Admin_Password
      This is the default admin password to log into ExamDeveloper.

    • BASIC_AUTH_USER_NAME=examDeveloper
      This is the API login username.

    • BASIC_AUTH_PASSWORD=Dummy_Password
      This is the API login password.

    • RABBIT_USER=ExamDeveloper
      This is the username of the RabbitMQ user with access to the above virtual host as created in Create a RabbitMQ user for EDRS.

       

      For side-by-side (additional instance)

      Icon

       

      For side-by-side (additional instance) installation, please ensure that the value specified for this variable is true for the new instance of ExamDeveloper. It should not be the one meant for any other existing instances of ExamDeveloper.

       

       

    • RABBIT_PASSWORD=Password
      This is the password of the RabbitMQ user with access to the above virtual host as created in Create a RabbitMQ user for EDRS.

       

      For side-by-side (additional instance)

      Icon

       

      For side-by-side (additional instance) installation, please ensure that the value specified for this variable is true for the new instance of ExamDeveloper. It should not be the one meant for any other existing instances of ExamDeveloper.

       

       

    • HANGFIRE_CONNECTION_STRING=Data Source=WIN-VSGF1NBSVPB;Initial Catalog=Hangfire;Persist Security Info=True;User ID=Hangfire;Password=P@s$w0rd
      The Initial Catalog name for "Hangfire" is the same as in step 6 of Creating new databases for Similarity and Hangfire. The user name and password for "Hangfire" is the same as in step 6 of SQL Server user management for Similarity and Hangfire.

      Icon
      This is an optional parameter and you need to use it only if you are planning to use EDQSS (Item Similarity feature).

      For side-by-side (additional instance)

      Icon

       

      For side-by-side (additional instance) installation, please ensure that the values specified for this variable are true for the new instance of ExamDeveloper. These should not be the ones meant for any other existing instances of ExamDeveloper.

       

       

    • SIMILARITY_CONNECTION_STRING=Data Source=WIN-VSGF1NBSVPB;Initial Catalog=Similarity;Persist Security Info=True;User ID=Similarity;Password=P@s$w0rd
      The Initial Catalog name for "Similarity" is the same as in step 3 of Creating new databases for Similarity and Hangfire. The user name and password for "Similarity" is the same as in step 3 of SQL Server user management for Similarity and Hangfire.

      Icon
      This is an optional parameter and you need to use it only if you are planning to use EDQSS (Item Similarity feature).

      For side-by-side (additional instance)

      Icon

       

      For side-by-side (additional instance) installation, please ensure that the value specified for this variable are true for the new instance of ExamDeveloper. These should not be the ones meant for any other existing instances of ExamDeveloper.

       

       

    • CONNECTION_STRING=Data Source=WIN-VSGF1NBSVPB;Initial Catalog=ExamDeveloper;Persist Security Info=True;User ID=ExamDev;Password=P@s$w0rd
      • Data Source = Name of SQL Server instance. You can identify the name of the SQL Server instance being used for ExamDeveloper as detailed over here.

        Icon
         To learn how to identify the SQL Server instance when there are more than one instances, click here to expand...

        If you have more than one instances of SQL Servers, then you must select the one you need to connect to use with ExamDeveloper as shown in the Connection window below.

        You can later identify the name of the SQL Server instance by right clicking the Server node in the SQL Server, clicking Properties, then selecting General page in the left pane of the Server Properties page, and observing the Name in the right pane as shown below.

      • Initial Catalog = ExamDeveloper (which is the ExamDeveloper Database).

      • User ID = Username of the SQL Server User who owns the database. This was created during SQL Server Database Setup under SQL Server user management. In our example, this is "ExamDev".

      • Password = Password of the SQL Server who owns the database. This was created during SQL Server Database Setup under SQL Server user management. In our example, this is "P@s$w0rd".

         

      For side-by-side (additional instance)

      Icon

       

      For side-by-side (additional instance) installation, please ensure that the values specified for the CONNECTION_STRING property are true for the new instance of ExamDeveloper. These should not be the ones meant for any other existing instances of ExamDeveloper.



    • TRACKJS_APPNAME=

    • TRACKJS_TOKEN=

    • CAS_USERNAME=

    • CAS_TOKEN=


  3. Modify the ReportDeploy.exe.config file from the ExamDeveloper reports.zip as follows:

    1. Extract the <SVNFolder>\Web\reports.zip file into a folder.

    2. Navigate to the folder where reports.zip was extracted and edit the ReportDeploy.exe.config file to modify the value of the below key:

      <add key="reportFolderName" value="@{REPORT_DSN_FOLDER}"/>

       

    3. Save the modified ReportDeploy.exe.config file.

    4. Create a ZIP archive reports.zip from the contents of the folder where <SVNFolder>\Web\reports.zip was extracted earlier, and copy it to <SVNFolder>\Web\ and overwrite the existing reports.zip.

  4. Create a standard user "servuser" to handle all the microservices.

    Icon

    Please ensure that the users "servuser" and "Local Service" have write access to the EDRS output directory (EDRS_OUTPUT_DIR).

    The user "Network Service" should have write access to the directory storing the microservices log files (LOG_ROOT_DIR) and the directory where the application Asset folder and log files will be stored (DATA_ROOT).

    The user "IIS_IUSRS" should have write access to the directory where the application Asset folder and log files will be stored (DATA_ROOT).

    You can determine the actual folder locations by finding the actual values for these tokens in the self-hosted.properties file.

    The users can be granted write access permission to the folders as detailed over here.



  5. Open Windows PowerShell as Administrator.

  6. Bypass the PowerShell execution policy with the following command:

    Set-ExecutionPolicy bypass
     
  7. Store the credentials for "servuser" into a variable $c with the following command:

    $c = Get-Credential

    This prompts you for the credentials, which you must enter and click OK.

    Icon

    Please ensure that the User name is entered in the "domain-name\username" format; in our example it is "WIN-VSGF1NBSVPB\servuser".


     

  8. Store the path to the self-hosted.properties and secure.properties files located at C:\EnvProp\ and C:\SecProp\ respectively as in our example, into variables $p and $q respectively. Run the following commands:

    $p = "C:\EnvProp\self-hosted.properties"
    $q = "C:\SecProp\secure.properties"

    For the optional secure.properties file

    Icon

    For side-by-side (additional instance) installation, please ensure that separate self-hosted.properties and secure.properties files with unique values are used to be stored in these variables, such as beta-self-hosted.properties and beta-secure.properties.

    For side-by-side (additional instance)

    Icon

     

    For side-by-side (additional instance) installation, please ensure that a separate self-hosted.properties file with unique values is used to be stored in this variable, such as beta-self-hosted.properties.

     


  9. Store the environment into a variable $e with the following command:

    $e = "prod" 

    For side-by-side (additional instance)

    Icon

     

    For side-by-side (additional instance) installation, please ensure that this value is set to a unique value that is different from the values used for other existing instances of ExamDeveloper, such as "beta" if you have used "prod" for the earlier instance.

     

  10. For the ItemBank service:

    1. Change the directory to the ItemBank service setup folder with the following command:

      cd "<SVNFolder>\ItemBank\"

      Where, <SVNFolder>\ItemBank\ is the location where the ItemBank service setup files have been downloaded.
      Please make sure that the ItemBank service setup path is enclosed in quotes, especially if the path name contains spaces.
       
    2. Run the following command to install the ItemBank service:

      ./setup.ps1 -Credential $c -PropertiesFilePaths $p,$q -Environment $e
       

      For side-by-side (additional instance)

      Icon

       

      For side-by-side (additional instance) installation, please add the parameter "-SideBySideInstall" to the above command.



  11. For the ExamService service:

    1. Change the directory to the ExamService service setup folder with the following command:

      cd "<SVNFolder>\Exam\"

      Where, <SVNFolder>\Exam\ is the location where the ExamService service setup files have been downloaded.
      Please make sure that the ExamService service setup path is enclosed in quotes, especially if the path name contains spaces.
       
    2. Run the following command to install the ExamService service:

      ./setup.ps1 -Credential $c -PropertiesFilePaths $p,$q -Environment $e 

      For side-by-side (additional instance)

      Icon

       

      For side-by-side (additional instance) installation, please add the parameter "-SideBySideInstall" to the above command.



  12. For the Project service:

    1. Change the directory to the Project service setup folder with the following command:

      cd "<SVNFolder>\Project\"

      Where, <SVNFolder>\Project\ is the location where the Project service setup files have been downloaded.
      Please make sure that the Project service setup path is enclosed in quotes, especially if the path name contains spaces.
       
    2. Run the following command to install the Project service:

      ./setup.ps1 -Credential $c -PropertiesFilePaths $p,$q -Environment $e
       

      For side-by-side (additional instance)

      Icon

       

      For side-by-side (additional instance) installation, please add the parameter "-SideBySideInstall" to the above command.



  13. For the User service:

    1. Change the directory to the User service setup folder with the following command:

      cd "<SVNFolder>\User\"

      Where, <SVNFolder>\User\ is the location where the User service setup files have been downloaded.
      Please make sure that the User service setup path is enclosed in quotes, especially if the path name contains spaces.
       
    2. Run the following command to install the User service:

      ./setup.ps1 -Credential $c -PropertiesFilePaths $p,$q -Environment $e
       

      For side-by-side (additional instance)

      Icon

       

      For side-by-side (additional instance) installation, please add the parameter "-SideBySideInstall" to the above command.



  14. For the Assignment service:

    1. Change the directory to the Assignment service setup folder with the following command:

      cd "<SVNFolder>\Assignment\"

      Where, <SVNFolder>\Assignment\ is the location where the Assignment service setup files have been downloaded.
      Please make sure that the Assignment service setup path is enclosed in quotes, especially if the path name contains spaces.
       
    2. Run the following command to install the Assignment service:

      ./setup.ps1 -Credential $c -PropertiesFilePaths $p,$q -Environment $e
       

      For side-by-side (additional instance)

      Icon

       

      For side-by-side (additional instance) installation, please add the parameter "-SideBySideInstall" to the above command.



  15. For the Question service:

    1. Change the directory to the Question service setup folder with the following command:

      cd "<SVNFolder>\Question\"

      Where, <SVNFolder>\Question\ is the location where the Question service setup files have been downloaded.
      Please make sure that the Question service setup path is enclosed in quotes, especially if the path name contains spaces.
       
    2. Run the following command to install the Question service:

      ./setup.ps1 -Credential $c -PropertiesFilePaths $p,$q -Environment $e

      For side-by-side (additional instance)

      Icon

       

      For side-by-side (additional instance) installation, please add the parameter "-SideBySideInstall" to the above command.



  16. For the Notification service:

    1. Change the directory to the Notification service setup folder with the following command:

      cd "<SVNFolder>\Notification\"

      Where, <SVNFolder>\Notification\ is the location where the Notification service setup files have been downloaded.
      Please make sure that the Notification service setup path is enclosed in quotes, especially if the path name contains spaces.
       
    2. Run the following command to install the Notification service:

      ./setup.ps1 -Credential $c -PropertiesFilePaths $p,$q -Environment $e
       

      For side-by-side (additional instance)

      Icon

       

      For side-by-side (additional instance) installation, please add the parameter "-SideBySideInstall" to the above command.



  17. For the Statistics service:

    1. Change the directory to the Statistics service setup folder with the following command:

      cd "<SVNFolder>\Statistics\"

      Where, <SVNFolder>\Statistics\ is the location where the Statistics service setup files have been downloaded.
      Please make sure that the Statistics service setup path is enclosed in quotes, especially if the path name contains spaces.
       
    2. Run the following command to install the Statistics service:

      ./setup.ps1 -Credential $c -PropertiesFilePaths $p,$q -Environment $e

      For side-by-side (additional instance)

      Icon

       

      For side-by-side (additional instance) installation, please add the parameter "-SideBySideInstall" to the above command.



  18. For the Asset service:

    1. Change the directory to the Asset service setup folder with the following command:

      cd "<SVNFolder>\Asset\"

      Where, <SVNFolder>\Asset\ is the location where the Asset service setup files have been downloaded.
      Please make sure that the Asset service setup path is enclosed in quotes, especially if the path name contains spaces.
       
    2. Run the following command to install the Asset service:

      ./setup.ps1 -Credential $c -PropertiesFilePaths $p,$q -Environment $e

      For side-by-side (additional instance)

      Icon

       

      For side-by-side (additional instance) installation, please add the parameter "-SideBySideInstall" to the above command.

  19. For EDRS:

    1. Change the directory to the EDRS setup folder with the following command:

      cd "<SVNFolder>\EDRS\"

      Where, <SVNFolder>\EDRS\ is the location where the EDRS setup files have been downloaded.
      Please make sure that the EDRS setup path is enclosed in quotes, especially if the path name contains spaces.
       
    2. Run the following command to install EDRS:

      ./setup.ps1 -Credential $c -PropertiesFilePaths $p,$q -Environment $e
       

      For side-by-side (additional instance)

      Icon

       

      For side-by-side (additional instance) installation, please add the parameter "-SideBySideInstall" to the above command.



  20. Icon

    EDSS setup is optional, so you need to follow these steps only if you plan to use EDSS.


    For EDSS:

    1. Change the directory to the EDSS setup folder with the following command:

      cd "<SVNFolder>\EDSS\"

      Where, <SVNFolder>\EDSS\ is the location where the EDSS setup files have been downloaded.
      Please make sure that the EDSS setup path is enclosed in quotes, especially if the path name contains spaces.
       
    2. Run the following command to install EDSS:

      ./setup.ps1 -Credential $c -PropertiesFilePaths $p,$q -Environment $e

       

      For side-by-side (additional instance)

      Icon

       

      For side-by-side (additional instance) installation, please add the parameter "-SideBySideInstall" to the above command.

       

  21. Icon

    EDQSS setup is optional, so you need to follow these steps only if you plan to use EDQSS.


    For EDQSS:

    1. Change the directory to the EDQSS setup folder with the following command:

      cd "<SVNFolder>\EDQSS\"

      Where, <SVNFolder>\EDQSS\ is the location where the EDQSS setup files have been downloaded.
      Please make sure that the EDQSS setup path is enclosed in quotes, especially if the path name contains spaces.
       
    2. Run the following command to install EDQSS:

      ./setup.ps1 -Credential $c -PropertiesFilePaths $p,$q -Environment $e

       

      For side-by-side (additional instance)

      Icon

       

      For side-by-side (additional instance) installation, please add the parameter "-SideBySideInstall" to the above command.

       

       

  22. For the ExamDeveloper application:

    1. Change the directory to the ExamDeveloper setup folder with the following command:

      cd "<SVNFolder>\Web\"

      Where, <SVNFolder>\Web\ is the location where the ExamDeveloper setup files have been downloaded.
      Please make sure that the ExamDeveloper setup path is enclosed in quotes, especially if the path name contains spaces.
       
    2. Run the following command to install ExamDeveloper:

      ./setup.ps1 -PropertiesFile $p -SecurePropertiesFile $q -Environment $e

 

 

Return to the top of the page.

 Configure automatic email notifications

 Set up prerequisites for SearchService (EDSS) and Enemy Detection (EDQSS)

 ExamDeveloper setup home page

 

  • No labels