You can run servers in Admin mode to perform maintenance on the server without allowing connections from your application end users. In Admin mode, the server accepts connections from EAServer Manager, jagtool, and clients that set the admin ORB option (described further below). A server that is accepting regular client connections is said to be in Ready mode.
In some cases, a server may switch to Admin mode when starting if a configuration problem prevents normal operation. For example:
The server is in a cluster, and its cluster version and start-up mode properties indicates that the configuration is not synchronized with the master configuration. In this case, you must synchronize the cluster as described in “Synchronization”.
The message service is installed, but cannot start for some reason such as failure to connect to the remote database server that stores message data. In this case, you must correct the configuration problem as described in Chapter 8, “Setting up the Message Service.”
When the server starts in Admin mode, or switches to Admin mode, it logs a message like this:
The server is in "admin" mode (reason).
where reason is text that describes why the server is in Admin mode. You see a similar message in EAServer Manager when you connect to a server running in Admin mode. With jagtool, you can check whether the server is in Admin mode with the getserverinfo command. In a custom management client, you can call the Jaguar::Management::getStatus() method: a return value of “ready” indicates normal operation. Any other value is text describing the reason the server is in Admin mode.
