Integration environments
TraX provides two integration environments referred to as the development- and production environments. Each environment uses its own distinct set of 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.
Common for both the development and the production environment
Web API
Server URL and token endpoints are provided in the TraX web API reference.
Message broker
The brokers run in an active/passive setup, i.e. at a given time, either broker-1 or broker-2 is active. We strongly RECOMMEND that you configure your TraX client to connect using a failover transport to connect to multiple broker endpoints.
Protocol | Broker instances |
---|---|
OpenWire |
|
STOMP |
|
STOMP |
|
WSS |
|
AMQP |
|
MQTT |
|
Development environment
Message broker queue names
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
Message broker queue names
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.