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

AVEVA Enterprise SCADA

Add components for deployment

  • Last UpdatedApr 24, 2025
  • 1 minute read

Note: For information on overriding default configuration of Business Logic Tier (BLT) components, see Modify configuration of Business Logic Tier (BLT) components.

Each Business Logic Tier (BLT) application is configured using a JSON configuration file located in either the default install root (%DNAInstallRoot%), or in the custom data root (%DNADataRoot%). Each configuration file must follow a naming convention:

<AppName>.json

For instance, the Arbitration BLT components are configured as one application in the Arbitration.json file, which can be found in the %DNAInstallRoot%\Common\config\BLT directory.

To customize the configuration of a BLTHost application

  1. Create an <AppName>.json file in the %DNADataRoot%\<Silo>\config\BLT directory.

  2. Add the following lines to the new <AppName>.json file:

    {

    "YourNewComponent2DllName.dll":

    {

    "YourNewComponent2DllName": [ "DNA Permission - View" ]

    },

    "YourNewComponent3DllName.dll":

    {

    "YourNewComponent3DllName": [ "DNA Permission - View" ]

    },

    "YourNewComponent4DllName.dll":

    {

    "YourNewComponent4DllName": [ "DNA Permission - View" ]

    }

    }

  3. Save your changes

    The outer most key (that is, YourNewComponent.dll) represents the file name containing one or more BLT components. The inner key (that is, YourNewComponent) represents the name of the BLT component to be configured. The inner key value is a list of permissions required to invoke the BLT.