Service mode register decode import
Use the following procedure to configure a task template:
-
Go to System Operations > Task Management > Task Templates.
-
Use the dropdown menu to select the Task Type and Task Template. (Click Add to create a new task template. For more information, see Adding task templates.)
-
Configure the Task specific parameters. These parameters are defined after step 5 of this procedure.
-
Configure the Common task template parameters. For more information, see Task template parameters.
-
Click Save.
Task specific parameters:
Backup File
Defines the file path to a directory where IEE creates a backup file of the readings as it imports them to the database. Enter the directory path where IEE writes the backup reading files.
Import Directory
Defines the folder that IEE monitors for incoming files. IEE automatically schedules files that arrive in this directory for import. You define the paths to default import directories in the IEE System Administration workbench. When configuring the import directory parameter in an import task template, enter the file path to the directory that IEE monitors for import files specific to this task. This parameter supports standard IEE macros. Reference as ($ImportDirectory) when configuring a task.
Owner of Import Tasks
Defines the user ID associated with a task. By default, this field populates with the user currently logged into IEE.
External System
Defines any external system to which IEE configuration data can be associated. In many places this parameter provides you with the dropdown menu to select from the external systems configured in the External System table.
Processing Chunk Size
Defines the number of configuration entities processed by sub-tasks. IEE groups the data that was processed by the task into separate batches of the size you designate here. IEE considers the task completed when all child tasks are finished, and each has reported back to the parent tasks.
Chunk size is a parameter common to several task templates. The higher the chunk size value, the greater the portion of the total available work each IEE task runner performs. A smaller value means dividing the work between more concurrent task runners.
Chunk sizes that are too large overburden a few task runners, while other task runners sit idle. In extreme cases, overly large chunk sizes could result in system failure due to lack of available, allocated memory. Chunk sizes that are too small spawn many task runners that perform more initialization and shutdown than actual work. Both large and small extremes will cause delays in export processing.
When fine tuning chunk sizes, consider database resources, hardware requirements, daily processing levels, and processing windows. Adjust values over time, as hardware and networking conditions change.
Task Template ID for a ReadingXMLExport Task
Defines the ID of the Reading XML Export task, so the Service Mode Decode Import task can automatically trigger an XML export. The import task can perform an export of reading and configuration data using the parameters specified in the Reading XML Export Task Template.