AMI Service Configuration
To make the following optional changes, update the configuration file Miner.Responder.RxIF.AmiService.exe.config located in:
C:\Program Files (x86)\Miner and Miner\Responder\Integration\Ami Service (or the installed path, if it was changed during installation).
-
Change the log file location, if required. By default the log file is placed in C:\Responder\Logs.
<file value="C:\responder\logs\Miner.Responder.RxIF.AmiService.log" />
-
Change the MSMQ ComputerName to the FQDN of the Responder Server.
Verify that the ComputerName is not populated, it should say ComputerName.
<wellknown type="Miner.Responder.Shared.IDataServices, Miner.Responder.Shared" url="msmq://FormatName:DIRECT=OS:{ComputerName}\private$\RxServer/DataServices.rem" />Set the ComputerName here:
<channel type="Miner.Responder.Shared.Channels.MSMQ.MSMQChannel, Miner.Responder.Shared" ComputerName="ComputerName " responseTimeout="00:06:00" />
-
Application Configuration
|
Config Key |
Config Description |
Default Config Value |
|---|---|---|
|
Ami.ProcessWaitInterval |
Time between two subsequent processing cycles |
00:00:30 |
|
Ami.StaleEventThreshold |
This setting is obsolete. The Stale Event Threshold must be configured in the Web Server. Please see the documentation for the Web Server you are using, either Multispeak or CIM. |
02:00:00 |
|
Ami.MomentaryEventThreshold |
This setting is obsolete. The Momentary Event Threshold must be configured in the Web Server. Please see the documentation for the Web Server you are using, either Multispeak or CIM. |
00:01:00 |
|
Ami.EventPersistDuration |
The amount of time to keep the meter events in the RXINT_METER_EVENT table before they are archived to the RXINT_METER_EVENT_HISTORY table. |
02:00:00 |
|
Ami.ArchivePersistDays |
Maximum number of days an event record is kept in the RXINT_METER_EVENT_HISTORY table. |
15 |
|
Ami.ArchiveInterval |
The frequency of running the job responsible for Archive and Delete from Archive. |
00:01:00 |
|
Ami.ChunkSize |
Number of calls submitted per request. Used in conjunction with the number of records retrieved by database view. The two numbers control how many dataservices would the AMI integration require. |
500 |
|
AMITimeToWait |
How far back to look for unrestored meters in seconds. |
180 |
|
AMIWaitInterval |
How often to check for unrestored meters in seconds. |
60 |
|
CreateNestedOutages |
If true, create nested outages for meters that Responder thinks are restored, but have not received a power up from AMI after waiting the AMITimeToWait amount of time |
False |
|
NestMode |
Determine how to create nested incidents. MultipleIncidents, SingleIncident, or Nest are options for this setting. |
MultipleIncidents |
|
NestComment |
Text to appear on COMMENTS for the Incidents created as a result of Nested Outage scenario |
AMI Nested Incident |
|
CheckResponderRestore |
If true, an additional check is done to get a list of meters restored recently. Power downs from those meters are then filtered out. This feature is meant to work in conjunction with the RxIF SCADA integration, so should be turned off if you do not have SCADA |
FALSE |
|
Ami.ResponderRestoredThreshold |
How far back to check Responder for recently restored meters |
0:10:00 |
|
EFCommandTimeout |
Entity Framework command time-out, in seconds. How long a sql command can run before it times out |
300 |