Please ensure Javascript is enabled for purposes of website accessibility
Powered by Zoomin Software. For more details please contactZoomin

AVEVA™ Work Tasks

TABLE OF CONTENTS

Add an Installation Path

Save PDF
Save selected topicSave selected topic and subtopicsSave all topics
Share
Share to emailCopy topic URL
  • Last UpdatedJun 14, 2024
  • 2 minute read

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, UI related files copied to a folder and required libraries added to the global assembly cache.

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 AVEVA Work Tasks libraries, 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>

  3. Add the libraries and dlls from the <drive>:\<custom_folder_path>\Bin folder to Global Assembly Cache (GAC). This can be performed by the installer or using the Visual  Studio Command Prompt.

    Use the following command to add the Dlls to GAC:

    gacutil /i "<drive>:\<custom_folder_path>\Bin\Workflow.NET.NET2.dll"

    Example

    Considering that the path <drive>:\<custom_folder_path> created in step 1 is C:\Program files\AVEVA\Work Tasks\, the following command must be used to add Workflow.NET.NET2.dll to GAC using Visual Studio Command Prompt.

    gacutil /i "C:\Program files\AVEVA\Work Tasks\\Bin\Workflow.NET.NET2.dll".

  4. Repeat step 3 to add all the dlls to the GAC from the Bin folder except for the following dlls:

    • ASmsCtrl.dll

    • CustomAction.NET2.dll

    • LumiSoft.Net.dll

    • Skelta.HWS.SampleApp.CustomDocView.dll

    • Workflow.NET.ActionHandler.MSOfficeActions.NET2.dll

    • Workflow.NET.SMS.Messenger.NET2.dll

    • Workflow.NET.SMTPManagedSink.NET2.dll

    • Interop.AxMmCtlLib.dll

    • Microsoft.WindowsAzure.Diagnostics.dll

    • Microsoft.WindowsAzure.ServiceRuntime.dll

    • Microsoft.WindowsAzure.StorageClient.dll

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