If you plan to build your own custom application, you can use the Generic HTTP Endpoint. The generic HTTP endpoint sends test result data or issue data in batches via HTTPS using HTTP Basic Auth. This option is the most amount of effort, as it requires you to create the necessary infrastructure to receive and process all the test result or issue data. In addition, since the transport mechanism is HTTPS, you also need to obtain an SSL certificate from a trusted CA for your destination. Self-signed certificates are not supported by the Generic HTTP data push.
The format of the messages sent by the generic HTTP data push follows the same schema below, the only difference is the messages are contained in a JSON list. There may be one or more test results or issues in each message. For example:
[
{test result},
{test result},
{test result}
]
To get started with the UXI Data Push Destination for the Generic HTTP Endpoint:
Create a server capable of handling all of the test result data. For an estimate, refer to the data estimation table. The server must accept connections via HTTPS using Basic Auth.
In the UXI dashboard, go to Settings > Integrations. In the Data Push Destinations section, click on the Add Destination button.
Specify the following information from the Add Destination modal that appears:
Name – Give the destination a friendly name
URL – Enter the hostname of your server. This server must be reachable from our UXI cloud dashboard.
Username – Enter the HTTP Basic Auth username
Password - Enter the HTTP Basic Auth password
4. Click the Add button
The Generic HTTP Endpoint data push destination will retry 1 time per request with a timeout of 3000 ms between retries. If the Generic HTTP Endpoint data push goes into a failed state, it will attempt to restart every 30 minutes.