Exporter

Exporters need to be created when you want to have RRExchange react upon the arrival of new passings, e.g. show rank and time on a display board or trigger a HTTP post message.

In order to receive raw data passings and RRExchange can act upon them (e.g. to display rank and time on a displayboard or to trigger a HTTP POST), RR12 exchange needs to define an exporter to send data to us.

Online

Our RemoteRedirect webservice provides a bridge between RR12 working online that can only access public web servers and RRExchange running locally.

Protocol is https and host is raceresult.remoteredirect.com: https://raceresult.remoteredirect.com

The following exporter need to be configured in RR12 (Timing - Exporters & Tracking - Exporters):

URL	Export Data
HTTP(S) Post https://raceresult.remoteredirect.com/api/raceresult/exporter	Custom [Event.ID] & ";" & [RD_TimingPoint] & ";"&[Bib] & ";" & [RD_Time]

Offline

When working offline (e.g. checking out the event and using the local race result Web Server, RRExchange acts a REST API server to receive exporter data.

Protocol is http (not https) and host is localhost:8181 (no www, take care with the :): http://localhost:8181

URL	Export Data
HTTP(S) Post http://localhost:8181/api/raceresult/exporter	Custom [Event.ID] & ";" & [RD_TimingPoint] &";"& [Bib] & ";" & [RD_Time]

Online & Offline

Name can be defined as you like, e.g. RRExchange. Timing Point/Split and Filter can be set to whatever you need, however you can always filter in RRExchange as well - so best is to leave it on All.