Configure and manage a dcm4chee-arc-light archive device, AE titles, and storage descriptors through its administrative REST API

Steps

1. Access the archive's administrative REST endpoints directly under the /dcm4chee-arc/ context root; for example, GET /dcm4chee-arc/ctrl/status returns archive run state, GET /dcm4chee-arc/aets lists configured AE titles, and GET /dcm4chee-arc/storage lists storage descriptors.
2. Use GET /dcm4chee-arc/aes to retrieve full Application Entity objects including network connection details for all configured AEs.
3. To explore and test all available REST operations (including device config, queue management, and export scheduling), consult the Swagger UI pointing at the published openapi.json: http://petstore.swagger.io/index.html?url=https://dcm4che.github.io/dcm4chee-arc-light/swagger/openapi.json
4. DICOMweb clinical operations (QIDO-RS, WADO-RS, STOW-RS, UPS-RS, and archive-specific study/patient management) are served under /dcm4chee-arc/aets/{aet}/rs, where {aet} is the Application Entity Title.
5. The web UI is served at /dcm4chee-arc/ui2/ and is distinct from the REST API paths; do not mix UI path references with API calls.