Resolve Custom Dependent Files for SOA Assembly

The configuration settings for the AVEVA Work Tasks Object Access (SOA) assembly differs based on how the SOA assemblies are registered. SOA assemblies can be registered through Global Assembly Cache (GAC), Web Service, or physical path.

Register SOA Assembly from Global Assembly Cache

The Source Version field displays the version of SOA Assembly in the source environment. In the Target Version field, you can specify the version of SOA Assembly that you want to use in the target environment. If you do not specify the target version, the source version is considered while installing the package. The SOA Assembly from Global Assembly Cache gets installed in the GAC folder.

You can also package the identified custom dependent files which can be installed while installing the package in the target environment. In the Source Files box, in the Custom Dependent File section, enter the source file path of the files. Click Add row to add multiple rows to install additional files in the target environment.

Register SOA Assembly from a Physical Path

The Source Physical Path field displays the physical path of SOA Assembly in the source environment. You can also package the identified custom dependent files which can be installed while installing the package in the target environment. Click Add row to add multiple rows to install additional files in the target environment. Enter the source physical path of the dependent files.

If the source folder is relative to the AVEVA Work Tasks installed path, and the folder does not exist in the target environment, then a new folder is created and the files are copied to it. For example, if the path of the file, rating.dll, is C:\Program files\AVEVA\Work Tasks\\Web\BPMUITemplates\CustomFolder\rating.dll, then a new folder named CustomFolder is created in the target machine and rating.dll is copied to it.

If the source folder is not relative to the AVEVA Work Tasks installed path, then the files are copied to the [AVEVA Work Tasks Installed Path]\AVEVA\Work Tasks\bin folder. For example, if the path of the file, rating.dll, is E:\SOA99\ rating.dll, then rating.dll is copied to [AVEVA Work Tasks Installed Path]\AVEVA\Work Tasks\bin folder in the target machine.

The Install in Global Assembly Cache field is optional and is used to install the SOA assembly and custom dependent files in the GAC of the target environment. Check the Install in Global Assembly Cache box, if you want to install the files in the GAC of the target environment.

Click Delete Custom File icon to delete the selected row. The dependent files will not be added to the package template.

Register SOA Assembly from Web Service

When SOA Assembly is registered from Web Service, you must specify the Web Target Details. The Web Source Details field displays the Web Service values in the source environment.

If you select Authentication Type as Anonymous in the Source environment, then enter only the Web service URL in the Web Target Details field. In the target environment, if the web service requires Windows authentication, then you can change the Authentication Type to Windows and enter the user name, password, and domain information.

Note:

- You must clear the cache if you have changed the user name and password after registering a SOA Assembly from Web. Otherwise, SOA Assembly will consider the old credentials for authentication and it will not validate.

- Consider that in any repository, you have created a SOA Web Service for any activity. When you configure a workflow for the activity, and add the workflow to the package template, the SOA web service also gets packaged as
an associated artifact. Even though the SOA web service is not configured for the workflow, it still gets added to the package as it is configured for the activity.