Important: The CygNet Device Template Manager utility enables device type-specific device template file validation but it does not automatically correct errors found in your device template file(s). If you are performing an upgrade, you must first use the CygNet Service Migration Utility Correct errors in template files option for your current version of CygNet to check your device template files at the service level and to automatically repair many device template file errors. Then you must run the CygNet Device Template Manager utility to locate any errors the CygNet Service Migration Utility did not catch and repair. See the CygNet Upgrade Procedure for more information.
The CygNet Device Template Manager utility (DtfMgr.exe) is useful for validating device template files (both .dtf and .xml) against the current validation rules of a specific EIE, loading valid device template files to a Device Definition Service (DDS), and comparing differences between device template files, among other things.
Deviations from a device template file's validation rules appear in the Results field of the CygNet Device Template Manager utility. These results help you to troubleshoot problems with your device template file. If you find that your device template file is invalid, open it in an XML editor and make the required changes. Once your device template file is in line with the appropriate device-specific validation rules, use the CygNet Device Template Manager utility to (re)load your valid device template file to the DDS.
The CygNet Device Template Manager utility is stored in the CygNet\Utilities directory (DtfMgr.exe) on the host server. To start the utility, use Windows Explorer to browse to the directory and double-click the program icon.
Note: You can also set up this utility to be installed and launched (started) via CygNet Client Installer so that the application can be version managed. See Version Management for instructions on how to do this.
For more information, see the subsections below:
For more information about device template file validation, see Validating Templates and template file subsections specific to your remote device types.
|
| Sample CygNet Device Template Manager Dialog Box |
To Validate an Unloaded Device Template File
To Validate All Device Template Files in a DDS
Note: The following procedure is useful if you are performing a CygNet upgrade because CygNet device template file validation rules change from release to release. Validating all deployed device template files at once is more efficient than validating them one at a time. However, any issues found must be manually resolved one at a time before the device template file(s) can be reloaded into your DDS.
To Load a Device Template File
Important: If two device template files have the same file name and you load the new valid version to your DDS, it overwrites the old valid version.
To Compare Two Device Template Files
The following table lists and describes the various properties of the CygNet Device Template Manager utility.
| Property | Description |
|---|---|
|
DDS Service |
The name of the DDS affected by the validation and/or load. Carefully select the correct one. |
|
Template File Name |
The name of the device template file(s) you are validating and/or loading. File extension can be .dtf or .xml. |
|
Results |
This field displays the results of your validation and/or (re)load. Fails are clearly indicated, and notes provide information about the error(s). |
|
Clear Results |
Use this button to clear unwanted result information in the Results field. |
|
Load Template(s) |
Initiates the load of one or more device template files to the selected DDS. Important: If two device template files have the same file name and you load the new valid version to your DDS, it overwrites the old valid version. |
|
Validate Template(s) |
Initiates the validation of one or more device template files. |
|
View/Edit |
Enables the viewing and editing of a single device template file selected in the Template File Name field. It is useful for correcting invalid device template files on an ad hoc basis, then revalidating them in the CygNet Device Template Manager utility. If you use this button, the template opens in Notepad. Wildcards are not allowed for this operation because the CygNet Device Template Manager utility must know the specific device template file in order to open it for viewing. |
|
Synch Registry |
The Synch Registry button enables you to synchronize the client-side DDS registry with a connected host DDS. All device template files in the DDS are synchronized. Benefits include deleting all local device template file registry entries that no longer exist in the connected host DDS and ensuring that functionality between the client DDS and host DDS is consistent. |
|
Options |
Options include the following:
|
|
Close |
Click this button to exit the CygNet Device Template Manager utility. |
The following table lists and describes device-specific options found on the Options drop-down menu with their associated EIEs.
| Device Type | Description |
|---|---|
|
AutoCom EIE EProd EIE FB EFM3000 EIE FlowAuto EIE Lufkin MPC EIE Lufkin SAM EIE NuFlo EIE Totalflow EIE |
Item ID Map: Displays all Item IDs and their corresponding elements and data groups for a selected device template file. |
|
Benchmark EIE |
The following are all options for the device type selected:
|
|
Eagle EIE Modbus Realflo EIE Thermo EIE |
The following are all options for the device type selected:
|
|
FB Net EIE |
The following are all options for the device type selected:
|
|
Micro1C EIE Modbus EFM EIE Modbus Omni EIE |
The following are all options for the device type selected:
|
|
ProSoft EIE |
The following are all options for the device type selected:
|