Reconfigure RealTime database (RTDB) fields

You can change the Management of Change (MoC) configuration for RealTime database (RTDB) fields by modifying the database JSON configuration files and running the Schema Convert (SchemaConverter) to regenerate the types.txt file.

Note: Reconfiguration of the RTDB fields requires a system restart and may also have unknown impacts on system behavior. It is recommended to only perform this operation when it is absolutely necessary, if there will be no impact to the MoC package promotion or rollback process, and AVEVA support has been consulted.

To reconfigure RTDB fields

1. On the desktop, double-click the Windows PowerShell for DNA shortcut.

   Windows PowerShell for DNA opens.

2. Execute the following command:

   set-silo RealTime

3. Create a RealTime Developer Environment (refer to the AVEVA Enterprise SCADA Shared Components Developer documentation).

4. Navigate to the <DevEnvironment>\RealTime\database\schema directory, and add JSON files for the structures and/or tables that you want to override the MoC classification on. You can use the original JSON files in the installation directory as a reference (%DNAInstallRoot%\RealTime\database\schema).

   For example, to override the tolerance field on the analog table, you create the analog.json file in the analog table subfolder and add the classification override for that field.

   • To classify the field as a configuration field, add "classification": "Configuration".

     For example:

     {

     "name": "analog",

     "fields": [

     {

     "name": "tolerance",

     "classification": "Configuration"

     }

     ]

     }

   • To classify the field as a RealTime (operational) field, add "classification": "RealTime".

     For example:

     {

     "name": "analog",

     "fields": [

     {

     "name": "tolerance",

     "classification": "RealTime"

     }

     ]

     }

     Notes: When fields are contained within structures, the parent structure containing the Configuration fields are capable of being included on multiple tables (for example, analog, status, and rate tables), and the tables will usually use these fields as Configuration fields. However, if the table contains records that are created operationally rather than at configuration time, these operational tables can include a structure that contains fields marked as Configuration fields.
     
     To resolve this, you can classify the field that identifies the structure within the table definition as RealTime. This will override all fields within that structure, and the fields will not be considered Configuration fields for that table only.
     
     You can only override the field classification at the top level of the field table or structure.

     For example, to override the flag structure field for the analog table so that the entire structure is used operationally (RealTime only), add "classification": "RealTime" to the structure field for that table.

     {

     "name": "analog",

     "fields": [

     {

     "name": "flag",

     "classification": "RealTime"

     }

     ]

     }

5. Navigate to the <DevEnvironment>\RealTime\source directory, and delete any example projects or solutions that you do not want to build.

   Note: Do not delete the SchemaConverter solution and directory.

6. Select the Window icon to open the Start Menu.

7. In the search box, enter Developer Command Prompt for Visual Studio, and press Enter.

   The Visual Studio Developer Command Prompt appears.

8. Change the working directory to the location of the development environment build.xml file by typing cd <drive>:\Dev\RealTime.

9. Execute the following command:

   Msbuild build.xml

10. Distribute the generated root.txt and types.txt files in the <DevEnvironment>\RealTime\database\INTEL_NT directory to the servers that need to be reconfigured.

    Note: For more information, refer to the Shared Components Developer documentation.