Operate
Installing Stroom, keeping it running, checking that it is, and fixing it when it isn't.
Stroom is a system you run, not a service someone else runs for you. This section is for whoever is responsible for it: getting it installed, knowing whether it is working, and getting it working again.
Stroom does most of its work in the background and keeps going when a single piece of configuration is not what you intended, which is what lets a busy system stay up. The practical consequence is that confirming a change had the effect you wanted is a step worth taking, rather than something to assume.
Checking it works shows you where to look, and every page says what proves the answer. Monitoring is the standing version of the same question, for noticing before anyone asks. Troubleshooting is organised by symptom, for when the answer is not what you hoped, and Resetting is for when something has to start again.
The other pages here are about the system itself rather than the data moving through it: installing it, who can see and change what, how people sign in, how configuration reaches a node, the nodes and jobs that do the work, and backup and restore, which is worth reading before you need it rather than after.