Startup dependencies
Web Portal startup will fail when following dependencies aren’t available/healthy:
-
Multitenant Access Control
-
Database
In this case, wait for the availability of the depenencies and restart Web Portal containers.
Following dependencies will have an impact on Web Portal functionalities, but not disrupt the startup:
-
Master Data Management (facility filter on Dashboard)
-
RabbitMQ (when not reachable)
In this case, Web Portal will recover to full functionality when the dependent services are up and healthy.
RabbitMQ Dependency Scenarios
Scenario: RabbitMQ is not reachable
- Description
-
-
RabbitMQ instance is down, crashed, or not yet started
-
Network issue between Web Portal and RabbitMQ
-
- Behavior
-
-
Web Portal will start successfully
-
The health of the service will be degraded
-
Connection retries will continue in the background
-
- Impact
-
-
Web Portal will be functional with reduced capabilities
-
Full functionality will be restored automatically when RabbitMQ becomes available
-
Scenario: RabbitMQ is available but integration exchange is missing
- Description
-
-
RabbitMQ instance is running and reachable
-
Required integration exchange does not exist in RabbitMQ
-
- Behavior
-
-
Web Portal startup will fail
-
Service will not become ready
-
- Impact
-
-
Web Portal will not start
-
Ensure the integration exchange is properly configured in RabbitMQ before starting the Web Portal
-
Scenario: RabbitMQ becomes available later but integration exchange is missing
- Description
-
-
RabbitMQ was not reachable during Web Portal startup
-
Web Portal started successfully with degraded health
-
RabbitMQ becomes available later, but the integration exchange does not exist
-
- Behavior
-
-
Web Portal will stop when the connection to RabbitMQ is established and the missing exchange is detected
-
Service will not become ready
-
- Impact
-
-
Running Web Portal instance will stop
-
Ensure the integration exchange exists in RabbitMQ before making RabbitMQ available to the Web Portal
-