Check installation
The three installation methods differ, but the verification process is the same for all of them. It consists of two steps, because Web Management can already respond even though the runtime is not yet operational.
1. Is Web Management accessible?
Open it in your browser:
- Windows Setup: http://localhost:5000
- Docker container and Edge deployment: the host port to which you mapped the container port
8080, for example http://localhost:8080
If the login page or the management dashboard appears, this step is complete. If you cannot interact with the login page because its fields are locked, the initial user is missing—see First Login and Initial User.
2. Is the runtime ready?
Query the runtime's health endpoint at the same address:
curl -i http://localhost:8080/health/runtime/ready
| Response | Meaning |
|---|---|
200 | The runtime is ready for use—the installation is complete. |
503 | At least one check failed. /health/runtime/details lists which ones in JSON format—for example, the license manager if the demo runtime has expired. |
If the endpoint does not respond at all, either Web Management is not running or the address is incorrect. GET /health/runtime/live alone answers the question of whether the runtime process is running at all.
The runtime provides its health endpoints on a separate port that is accessible only from localhost. From the outside, access therefore goes through Web Management, which forwards the requests to /health/runtime/…. The complete list of endpoints and their checks can be found at Health endpoints .
If the runtime is not ready
Immediately after a Windows installation, this is the normal situation: The runtime is not yet running because no engineering has been performed yet. After the initial engineering, start it manually once—see Service Operation .