Map the plugin to a Batch Transfer source

There are two files to update prior to using the Batch Transfer source plugin located in “C:\Program Files\AVEVA\DNA\RealTime\config\Settings”.

Extending LMS.RealTime.json

For LMS.RealTime.json, the section “BatchDataHandlerAssemblies” in “BatchXfer” must be updated with the new plugin. In the following example, the “SOURCE_VFC” plugin is replaced with the newly created “VFCX”. Place the settings file in the %DNADataRoot%\RealTime\config\Settings\ directory. For an example, refer to the snippet shown below for the file named LMS.RealTime_override.json.

Note: The name of the file does not matter if it does not conflict with an existing file within the same directory.

• AssemblyName is your new plugin assembly name configured in the project settings.

• ObjectName is the name of your entry point class (that is, the one inheriting from the source type class or BatchTransferSourcePlugin).

Note: Only one implementation for each source type can run across the entire system as the baseline code currently performs simple mapping between the source type value and the configuration file entry.

Extending LMS_Extensions.json

The plugin is loaded using the standard OASyS extension architecture. To load your custom assemblies, create a .json file in the %DNADataRoot%\RealTime\config\Settings\ directory. For an example, refer to the snippet shown below for the file named LMS_Extensions_override.json.

Note: The name of the file does not matter if it does not conflict with an existing file within the same directory. In addition, it is not necessary to remove the configuration of the source type you are replacing. You can keep the baseline configuration as well as your configuration.

Applying the Changes

After extending LMS.RealTime.json and LMS_Extensions.json, restart the RealTime service for the changes to take effect.