Temetra Uploader is used to send files to Temetra, typically on an automated schedule, from your LAN to Temetra. This is most frequently used for keeping customer information synchronized, but can also be used to upload meter readings or logger data files that are generated periodically by another external system.
When you double click on Temetra Uploader, it presents a dialog where you configure the communication parameters, test communications with Temetra, and specify which files should be uploaded.
Once the configuration is correct, you can run the application on a schedule by specifying a configuration file on the command line:
TemetraUploader.exe --process
Temetra Uploader does all its communication from your host PC to Temetra over https (port 443) at www.temetra.com. This allows you to restrict access from the host PC using your firewall if required.
If the host PC accesses the Internet through a web proxy, you will need to configure the details. This minimum required information is the proxy address and port number - leave the name, password and domain blank if these are not required.
Authentication during uploading is done with an API token you receive from Temetra. This is a long character string that uniquely identifies your upload instance, and determines the target network on Temetra. Once you've entered this token, you can use the ""Test Comms"" button to confirm that the uploader is able to successfully communicate with Temetra, without doing an actual file upload. This ensures that all firewall and proxy setting are working OK in advance of scheduled uploads.
Temetra Upload will only upload the files specified using standard
Windows wildcard characters. For Agresso customer and meter details,
this will be L1Meters.xml or L?Meters.xml to
allow L1Meters.xml, L2Meters.xml, etc to be uploaded.
For Agresso arrears file, you should add balances.csv
For customers responsible for multiple Temetra networks, it may be necessary to upload files to different networks from the same upload location.
This can be achieved with Temetra Uploader using different configuration files. When you double click on Temetra Uploader, it will open the configuration file default.tuc and edit this. If you make changes and click the ""Save"" button, it will save the details back to default.tuc.
Use the ""Save As..."" button to save a different configuration file, and ""Open..."" to load a different configuration file. In this way, you can save multiple configuration files, and then schedule them independently. Be sure to use the correct API token for each corresponding network, since this will determine where the file will be uploaded.
Once the individual configuration files are saved, you can schedule them independently:
TemetraUploader.exe --process network-a.tuc
TemetraUploader.exe --process network-b.tuc
TemetraUploader.exe --process network-c.tuc
When the uploader runs, a log file is produced in the same directory as the executable (usually
C:\Program Files\Temetra\Temetra Uploader). It will be called temetra-uploader.log. This can be helpful when trying to determine why a unattended, scheduled upload did not work as expected.