Add an Installation Path

You can define a custom installation path where AVEVA Work Tasks components will be copied during custom installation process. To enable AVEVA Work Tasks on a machine it is mandatory to have the components and UI related files copied to a folder.

To add an Installation Path

1. Create a directory in the machine where all AVEVA Work Tasks components and UI files will be copied.

   Example

   <drive>:\<custom_folder path>

   Note: The <drive>:\<custom_folder path> mentioned above can be any drive path on the machine where you would like to install AVEVA Work Tasks in custom installation mode.

2. During installation process, copy UI related folders and files to the custom folder created. The files and folders required to be copied are:

   • BAMReports

   • Bin

   • DatabaseScripts

   • Locales

   • Logs

   • Documentation

   • WorkflowManagementWebService

   • Web

   • WorkflowElements

     Copying contents of Logs folder are an exemption.

     Copy security_approval_workflow.xml from AVEVA Work Tasks installation path to custom path, <drive>:\<custom_folder_path>

     The libraries and dlls are installed in the following folders:

   • C:\Program Files\AVEVA\Work Tasks\Bin

   • C:\Program Files\AVEVA\Work Tasks\Web\EnterpriseConsole\bin

   • C:\Program Files\AVEVA\Work Tasks\Web\CentralConfig\bin

   • C:\Program Files\AVEVA\Work Tasks\Web\ECSite\Bin

   • C:\Program Files\AVEVA\Work Tasks\Web\Quickflow

   • C:\Program Files\AVEVA\Work Tasks\Web\Workflow.WebAPI\Bin

To add the installation path mentioned in step 1 to the registry, refer section Entry for AVEVA Work Tasks Folders.

Note: All binaries are removed from the Global Assembly Cache (GAC) and placed in the Central Configuration and Enterprise Console bin directories. For custom applications referencing Work Task DLLs from the GAC, copy the required binaries to the application's bin directory and update the web.config file accordingly.
Any Work Tasks binary entry in the custom application's web.config file should be removed once the specified binary is placed in the application's bin directory.