SCADA Post Installation Configuration

Update the application configuration file Miner.Responder.RxIF.ScadaOutbound.exe.config located in:

C:\Program Files (x86)\Miner and Miner\Responder\Integration\Scada Outbound Service

or in the installed path if it was changed during installation.

  1. If required, Change the log file location. By default the log file will be placed in C:\Responder\Logs.

    <file value="C:\Responder\Logs\Miner.Responder.RxIF.ScadaOutboundService.log" />

  2. Change the MSMQ ComputerName to the FQDN of the Responder Message Router 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:02:00" />

  3. Application Configuration

    Config Key

    Config Description

    Default Config Value

    ScadaInterface.ServiceName

    Configuration for the Outbound service to Identify the Scada Service Specification

    Multispeak30ab

    ProcessWaitInterval

    Time between two subsequent processing cycles

    00:00:15

    Multispeak.ApplicationName

    Standard detail for the Outbound message header.

    Responder OMS

    Multispeak.ApplicationVersion

    Standard detail for the Outbound message header.

    10.6.1a

    Multispeak.Company

    Standard detail for the Outbound message header.

    Schneider Electric

    Multispeak.UserID

    Standard detail for the Outbound message header.

    sample

    Multispeak.Password

    Standard detail for the Outbound message header.

    sample

    CallRemarks

    Remarks on Calls created by IVR.

    Remarks on Calls created by IVR.

    IvrCallRecordId

    Custom field added to the RX_CALLS table to maintain the call ID for a call record in the IVR system. Used when callbacks or close calls requests are submitted once the incident is restored.

    RXINT_CALL_RECORD_ID

    StaleEventThreshold

    EVENTTIME timestamp in HTTP endpoint data received over this threshold compared to system time are not processed and are errored out back to the source system.

    02:00

    MomentaryEventThreshold

    Time between PowerDown and PowerUp events that are within this threshold are considered momentary. Note: if the RECIEVETIME of the event at the HTTP endpoint is greater than the PowerUp EVENTTIME, then the event will not be treated as momentary.

    00:00:30

    FilterDuplicates

    Multiple incidents will not be created when SCADA events are created for the same device.

    TRUE

    Scada.EventMap

    The optional configuration available to map the SCADA system status to the Responder device status.

    Scada.EventMap

    ScadaIncidentRemarks

    Remarks on Incidents created because of SCADA device operation

    Created by SCADA.

    ScadaClassModelName

    Class model name to be assigned to identify the SCADA device in the geodatabase.

    SCADAFEATURECLASS

    ScadaFieldModelName

    Field model name to identify the Scada Device using the Field assigned this model name.

    SCADADEVICEID

  4. Change the MockServices URL to point to your SCADA system’s web services. The underlined portion in the code below needs to be changed in both places. The new endpoint address will look similar to http://123.456.78.9/msscada/SCADA.
    <client>
    <!-- Multispeak 416 Scada Service config -->
    <endpoint address="http://localhost/Miner.Responder.RxIF.MockServices/ScadaServer416.asmx" binding="basicHttpBinding" bindingConfiguration="SCADA_ServerSoap" contract="Multispeak416ScadaService.SCADA_ServerSoap" name="ScadaServer416Soap"/>
    <!-- Multispeak 30ab Scada Service config -->
    <endpoint address="http://localhost/Miner.Responder.RxIF.MockServices/ScadaServer30ab.asmx" binding="basicHttpBinding" bindingConfiguration="SCADA_ServerSoap" contract="Multispeak30abScadaService.SCADA_ServerSoap" name="ScadaServer30abSoap"/>
    </client>
  5. If you are using Multispeak3.0ab, you’ll need to change the commenting on a couple items. You will need to comment out the line for Multispeak4.1.6, and uncomment the line for Multispeak3.0ab, so the two lines looks as follows:
        <add key="ScadaInterface.ServiceName" value="Multispeak30ab"/>
        <!--<add key="ScadaInterface.ServiceName" value="Multispeak416"/>-->
QR Code is a registered trademark of DENSO WAVE INCORPORATED in Japan and other countries.

Was this helpful?