The 'Server Manager' tab of the UConsole allows one to manage a single UltraESB node connected to via the UConsole. The 'Server Operations' tab shows the current state of the instance, and allows a node to be restarted, stopped (but do not exit JVM to allow a subsequent re-start), shutdown (stop and exit JVM), put into a maintenance mode (where new requests will be rejected, but already accepted messages processed) or shutdown gracefully (waiting for a specified time until an idle state is reached).
The 'Server Configurations' tab allows the user to load, unload or re-load a dynamic configuration fragment (e.g. conf/ultra-dynamic.xml). By default, the UltraESB configuration fragments found in the conf directory of the instance is shown, along with its current state and controls for management. A dynamic configuration update is performed atomically to ensure that a message flow does not see different versions of the configuration. Hence, after a configuration is unloaded, its retained in memory until the administrator explicitly purges such configurations after some time. Usually such outdated configurations consumes only a very small amount of RAM, and a purge is not required at all for almost all UltraESB production deployments.
Labels