Getting started with ARI

Before you start using ARI and the ARI Dashboard, you must configure ARI and its components for optimal performance. Configuring ARI is an involved task. For more information, see the IEE AMI Readings Import Guide.

A typical ARI configuration process requires completing the following procedures:

• Verify that your system hardware and software meet the minimum requirements to support ARI processing.

• Create the required directories for ARI processing.

  • Readings

  • Workbin

  • Workbin0

  • Resubmit

• Configure database settings.

• Configure ETL settings.

• Define system settings.

• Add a row to the External System Code Table for each external system that collects ARI data.

• Create a task service (ETL Runner) that is dedicated to daily incremental ETL tasks.

• (Optional) Configure web services authentication between IEE and the collection system.

• Set DeviceCommService attribute values on each IEE application server.

• Define callback addresses for asynchronous operations in the appropriate code tables.

• Configure the AMI readings import service.

• Verify that your VE services are configured.

• Configure a Reading XML Import Task Template.

• Depending on your database, either:

  • Configure the Oracle importer job.

    or

  • Configure the import task in Microsoft SQL Server.

• Configure the ARI Cleanup Task.

• Configure a task template for the AMI Message Summary ETL.

• For every task type, create at least one task template for each external system.

• Create recurring schedules to run routine tasks that don't require specific data to be present for successful completion.