Processing tab

From the AMI Data Export task template Processing tab, you can define properties that control the export processing and deletion of old requests that have been completed. The following parameters are specific parameters related to the AMI Data Export task template:

Defines the external system that is making the request. External systems must be configured in the External System code table in the System Administration workbench to appear here. For more information about how to configure the External System code table, see External system table.

Do not use the default task template. For every task type, create at least one task template for each external system, even if all of the parameters are the same. For example, if you have two external systems receiving data from the AMI Billing Export task type, create a separate task template for each external system.

ClosedExport Mode

Defines how the results are returned. The valid values are as follows.

  • Free Flow. Export request entities individually as each entity is ready for export.

  • Batch. Export all requested entities in a single batch. All entities must be ready for export before any of the entities are exported.

The default value is Free Flow.

ClosedForce Complete

Determines whether data is forced to export even though one or more channels do not have data. Select this checkbox to force the export to complete with partial data. Clear this checkbox to force the export to wait for complete data. The default setting is a clear checkbox.

ClosedAggregate on Export

Determines whether an aggregation is run immediately before the export. Select to run the aggregation. Clear the checkbox to skip the aggregation. The default value is to skip the aggregation.

ClosedData Retention

Defines under what scenario data will be retained. The valid values are as follows.

  • Retain Requests on Exception. Only requests that have an exception are saved outside the export window.

  • Always Retain Requests. Save all requests.

The default value is Retain Requests on Exception.

Defines under what scenario data will be retained. The valid values are as follows.

  • Retain Requests on Exception. Only requests that have an exception are saved outside the export window.

  • Always Retain Requests. Save all requests.

The default value is Retain Requests on Exception.

ClosedRetention Days

Defines the number of days in the past to retain ADE request entries and any related child records in the database. Purging old requests maintains manageable database table sizes and ensures good performance of the ADE subsystem. Enter a positive integer.

ClosedChunk Size

Defines the number of request items grouped for internal processing in the ADE export service. Affects the number of entities that are retrieved from the AdeEntity database table during configuration fetches and data availability fetches. Affects the number of entities that are retrieved from the database during configuration fetches and data availability fetches.

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.

ClosedException Processing

Determines how to process exceptions. The default is to have all checkboxes in this group clear. The valid values are as follows.

  • Create an Exception When Request Item Expires. IEE creates an item in the queue that is associated with this task type.

  • Notify Requesting System on Exception. IEE sends a message to the requesting system indicating that the request cannot be completed. IEE does not complete the request.

  • Include Warnings in Output. IEE completes the request and includes exception messages in the data returned to the requesting system.

For more information about Task Template Parameters in the bottom pane, see Common Task Template Parameters.

Click Save.