Launcher Service — Управление сервисами платформы

To start and stop Directum RX services, the launcher CLI executes up, down, restart, and status actions across all services or specific components like webserver, postgres, rabbitmq, elasticsearch, and haproxy.

The best way to check Directum RX platform health is by running a targeted health check across all services or specific namespaces to quickly identify broken dependencies and validate readiness after changes.

To retrieve Directum RX logs for troubleshooting, you can fetch component-specific logs and review launcher logs to speed up incident diagnosis and root-cause analysis for platform failures.

Yes, you can restart specific Directum RX components by targeting a named service namespace such as webserver or postgres, allowing the rest of the stack to remain unaffected during maintenance.

On-prem Directum RX deployment management supports validating and encrypting configuration, reloading HAProxy config, managing DevelopmentStudio, and handling operational deployment tooling tasks.

Launcher service requires a working launcher_path discovery because it needs to locate the DirectumLauncher CLI executable to properly map supported Directum ports and endpoints for service management.