Before the first Web request is processed, the components have to start and pass some basic information. In general, this process runs as follows:
1. Start an AdminServer.
2. Start a database in multi-user mode with properties supplied by the AdminServer from the conmgr.properties file.
3. Start a NameServer with properties supplied by the AdminServer from the ubroker.properties file.
4. Start a WebSpeed broker with properties supplied by the AdminServer from the ubroker.properties file.
5. The broker spawns its WebSpeed agents using the information it received from the AdminServer.
By default, the broker sends a message every 30 seconds to notify the NameServer that it is still available to accept requests. If the NameServer does not get a message, it deletes the broker from its “available" list. These messages are not part of the request process.
6. The broker registers itself and the application services that it provides with the NameServer.
7. Start a Web server, which makes its WebSpeed Messenger available to transfer Web requests.
