Configuration Related Files

By default, Unified Engineering in AVEVA™ Unified Engineering – Browser Access tenant environments are configured with the following path EVARs:

EVARS can be (optionally) overridden using the ConfigFiles folder shared storage area accessed from P:\ drive:

• P:\ConfigFiles\

  

• P:\ConfigFiles\AuthorModify
  

  • Administrators with the AVEVA™ Unified Engineering – Browser Access Author CONNECT role (or via a CONNECT group that has this role) have modify permissions on this folder.

  • Authors with the AVEVA™ Unified Engineering – Browser Access Author CONNECT role (or via a CONNECT group that has this role) have modify permissions on this folder.

  • This allows you as an Administrator to place config-related files that Authors require write permissions on.
    For example, updateable PML files.

• P:\ConfigFiles\AuthorRead
  

  • Administrators with the AVEVA™ Unified Engineering – Browser Access Author CONNECT role (or via a CONNECT group that has this role) have modify permissions on this folder.

  • Authors with the AVEVA™ Unified Engineering – Browser Access Author CONNECT role (or via a CONNECT group that has this role) have read-only permissions on this folder.

  • This allows you as an Administrator to place config-related files that Authors require read-only permissions on.
    For example, read-only PML files.

  • This also allows you as an Administrator to place security reviewed reports in AVEVA™ Unified Engineering – Browser Access environments to ensure they are not modified by non-admins.

Within the AuthorRead folder there is a prepared custom_evars.bat file in which administrators can override default path EVARS. Unified Engineering is configured to access this custom_evars.bat by default:

Configuring Custom PML Macros for use from streamed desktops

An example of where ConfigFiles can be useful is configuring custom PML Macros for use in streamed desktops.

Users do not have administrator access in their streamed desktop and therefore do not have write permissions to Universal Windows Platform (UWP) Applications protected folders.

Unified Engineering is a UWP app that ships with default PML macros stored within a protected folder only accessible by the application itself. Therefore, it is not possible to add custom macros to this folder.

AVEVA™ Unified Engineering – Browser Access tenant environments provide a folder structure for Configuration Related Files to allow you as an Administrator to make custom PML Macros available to sessions.

The following illustrates how the folders can be used:

To make custom PML Macros available to Unified Engineering (GUI or TTY) for all projects:

1. Place the PML macros in to the
   P:\ConfigFiles\AuthorModify\PMLLIB\ folder (if you want Authors to have write permissions)
   or
   P:\ConfigFiles\AuthorRead\PMLLIB\ folder (if you want Authors to have read permissions)
   For the first-time, the PMLLIB folder will need to be created.

2. Add an entry to P:\ConfigFiles\AuthorRead\custom_evars.bat
   set PMLLIB= P:\ConfigFiles\AuthorModify\PMLLIB\;%PMLLIB%
   or
   set PMLLIB= P:\ConfigFiles\AuthorRead\PMLLIB\;%PMLLIB%
   as appropriate

To make custom PML Macros available to Unified Engineering sessions (GUI or TTY) for a specific <PROJECT>:

3. Place the PML macros in to the Working Project Files folder for the project

   1. P:\ProjectFiles\<CONNECT Account>\_<CONNECT Folder Level1>\_<CONNECT Folder Level2>\<Spectrum Project Name>\PMLLIB\

   2. For the first-time, the PMLLIB folder will need to be created.

4. Add an entry to P:\ConfigFiles\AuthorRead\custom_evars.bat

   3. Set PMLLIB= P:\ ProjectFiles\<CONNECT Account>\_<CONNECT Folder Level1>\_<CONNECT Folder Level2>\<Spectrum Project Name>\PMLLIB\;%PMLLIB%

Performance can be affected if a PML file stored on P:\ is accessed by the application a significant number of times.

Performance can be improved by using the PML STATISTICS command in the application and a buffering directive in the PML file:

• The PML STATISTIC command identifies those PML files performing a significant number of reads.

• The PML buffering directive forces retention of the file in memory indefinitely once it has been read a specified number of times.

For each high-read-rate PML file, insert a buffering directive (a dash and a number directly after the three-digit encryption algorithm ID) in the PML file header line (the first line in the file).

Example:

--<000-1>-- Published PML 1.1 >--

Where the "000" is the three-digit encryption algorithm ID and the "-1" implies to read the file once and thereafter retain in memory for further reads.

Full details can be found in the Buffering section of the PML Publisher User Guide.

(https://softwaresupportsp.aveva.com/#/producthub?q=pmlencrypt&selectedTab=Documents)