TraX offers two integration environments: one for development and one for production. Each environment has separate accounts and configurations (e.g., queues).
The development environment is provisioned first. The production environment is provisioned when the partner is ready for production activities.
Applicable to Both Development and Production Environments
Web API
Server URL and token endpoints are provided in the TraX web API reference.
Message broker
The brokers operate in an active/passive setup, meaning that at any given time, either broker-1 or broker-2 is active. We strongly recommend configuring your TraX client to use a failover transport, allowing it to connect to multiple broker endpoints.
Protocol | Broker instances |
---|---|
OpenWire |
|
STOMP |
|
STOMP |
|
WSS |
|
AMQP |
|
MQTT |
|
Development Environment
Queue naming pattern | Example | Used in |
---|---|---|
trax.[name-of-tsp]dev.sensor-configuration | trax.tspabcdev.sensor-configuration | Sensor Configuration Integration |
trax.[name-of-tsp]dev.vehicle | trax.tspabcdev.vehicle | Vehicle Store Integration |
Production Environment
Queue naming pattern | Example | Used in |
---|---|---|
trax.[name-of-tsp].sensor-configuration | trax.tspabc.sensor-configuration | Sensor Configuration Integration |
trax.[name-of-tsp].vehicle | trax.tspabc.vehicle | Vehicle Store Integration |
Comments
0 comments
Article is closed for comments.