Collapse All Expand All

Version: 10.2.1c and 10.2.1c SP3

Resource Center Home

Responder Mobile transfers data from Responder tables between the field and Enterprise. You can include additional tables to send more data to/from the field. Note that including more data will slow performance when sending/receiving tasks.

If you have modified the names of your Responder tables in DatabaseSChemalConfig.xml, then you will need to also modify these table names in Miner.Responder.MobileService.exe.config. This section discusses both of these customizations.

Add Tables

You can also include data from additional tables in the tranfer between the field and Enterprise. Be warned that adding data to the transfer can slow performance. To add a table, you will need to modify Miner.Responder.MobileService.exe.config. Follow the steps outlined below to include additional data:

1. Open Miner.Responder.MobileService.exe.config. By default, this file is installed here: C:\Program Files\Miner and Miner\Responder\Server.
2. Look for the following XML tags. You will add a <type> tag for each table to the <types> section.

   	Copy Code
   <container name="MobileTables"> <types>

3. You can copy an existing <type> section for a table and modify the relevant tags or you can use the sample provided below.

   Copy Code

   <type name="TABLENAME" type="Miner.Responder.Mobile.Interfaces.IMobileTable, Miner.Responder.Mobile" mapTo="Miner.Responder.Mobile.ResponderObjects.ResponderTable, Miner.Responder.Mobile" > <typeConfig extensionType="Microsoft.Practices.Unity.Configuration.TypeInjectionElement, Microsoft.Practices.Unity.Configuration"> <constructor> <param name="tableName" parameterType="System.String" > <value value="TABLENAME" type="System.String"/> </param> <param name="tableUniqueID" parameterType="System.String" > <value value="IDFIELDNAME" type="System.String"/> </param> <param name="TableForeignIncidentID" parameterType="System.String" > <value value="FOREIGNKEYTOINCIDENTSTABLE" type="System.String"/> </param> </constructor> </typeConfig> </type>

    

4. Modify the following tags to match your DatabaseSchemaConfig.xml file.
   • Type name: This value generally corresponds to the name of the table as it appears in DatabaseSchemaConfig.xml.
   • TableName value: This value must correspond to the name of the table as it appears in DatabaseSchemaConfig.xml.
   • TableUniqueID value: This value must correspond to the field name on the table that holds a unique ID to identify the row. In most cases this will be the foreign key. 
   • TableForeignIncidentID value: This value shows how the current table is related to the RX_INCIDENTS table. It must correspond to the field in the table you're editing that acts as a foreign key to the RX_INCIDENTS table.
5. Save and close Miner.Responder.MobileService.exe.config.

 

Modify Tables

By default the Miner.Responder.MobileService.exe.config file contains four Responder tables. The data in these tables is transferred between the field and Enterprise as needed. If you have modified the names of these tables, then you will need to modify the XML in Miner.Responder.MobileService.exe.config as well. The names of these tables MUST match the names in your DatabaseSchemaConfig.xml file.

RX_INCIDENT_DEVICES

RX_INCIDENT_FEATURES

RX_HAZARDS

RX_CREW_ASSIGNMENTS

To modify the table names, follow the steps outlined below.

1. Open Miner.Responder.MobileService.exe.config. By default, this file is installed here: C:\Program Files\Miner and Miner\Responder\Server.
2. Look for the following XML. The example shows the XML for just one table. You will find in the configuration file XML for all four tables listed above.

   Copy Code

   <type name="RX_INCIDENT_DEVICES" type="Miner.Responder.Mobile.Interfaces.IMobileTable, Miner.Responder.Mobile" mapTo="Miner.Responder.Mobile.ResponderObjects.ResponderTable, Miner.Responder.Mobile" > <typeConfig extensionType="Microsoft.Practices.Unity.Configuration.TypeInjectionElement, Microsoft.Practices.Unity.Configuration"> <constructor> <param name="tableName" parameterType="System.String" > <value value="RX_INCIDENT_DEVICES" type="System.String"/> </param> <param name="tableUniqueID" parameterType="System.String" > <value value="ID" type="System.String"/> </param> <param name="TableForeignIncidentID" parameterType="System.String" > <value value="INCIDENT_ID" type="System.String"/> </param> </constructor> </typeConfig> </type>

3. Locate the table you need to edit and modify the following attributes to match your DatabaseSchemaConfig.xml file.
   • Type name: This value generally corresponds to the name of the table as it appears in DatabaseSchemaConfig.xml.
   • TableName value: This value must correspond to the name of the table as it appears in DatabaseSchemaConfig.xml.
   • TableUniqueID value: This value must correspond to the field name on the table that holds a unique ID to identify the row. In most cases this will be the foreign key. 
   • TableForeignIncidentID value: This value shows how the current table is related to the RX_INCIDENTS table. It must correspond to the field in the table you're editing that acts as a foreign key to the RX_INCIDENTS table.
4. Save and close Miner.Responder.MobileService.exe.config.

 

 

---

Send Comment to ArcFMdocumentation@schneider-electric.com