Load Balancer - URI (Context) Based Routing
If you want to perform routing based on individual components, you need an application load balancer (layer 7). You must configure health-check for individual components and route requests based on the URI.
Prerequisite
- An application load balancer (layer 7) must be provisioned.
- All component-to-component communication should be via the application load balancer.
AE URI Paths
The following URI needs to be configured in the AE load balancer if URI based routing is required:
| Frontend URI | Component | Backend Health Check URI | Additional Information |
| /ts | Transaction Store (Open Distro) | /status/txnstore | |
| /messaging |
Messaging (Rabbit MQ) |
/status/messaging | |
| /reports-int | Reporting (Kibana) | /status/reporting | |
| /jw | LowCode | /status/lowcode | Is an optional component. It must be configured if you are planning to use LowCode. |
| /ml | Machine Learning | /status/ml | Is an optional component. It must be configured if you are planning to use Machine Learning. |
| /ui | Control Tower | /status/controltower | |
| /api | |||
| /ts-api | |||
| /reports | |||
| /messaging-sso | |||
| Default (any other URI) |
If a component is up and running, the health check API returns HTTP status code 200; however, if it is down, the API returns HTTP status code 503.
|
NOTE: |
For AMQP protocol, network load balancer is required. Network Load balancer name should be configred in ae.properties file: |