Managing and Monitoring the OpenROAD Server
Overview of the OpenROAD Server Manager
This chapter describes how to manage and monitor the OpenROAD Server using the OpenROAD Server Manager. This chapter describes:
• The Server Manager environment
• Interfaces between the Server Manager and ASOLib
• The Server Manager interface, and how to start it
• Configuration options for Name Servers and the Server Pooler (SPO)
For more information about the Manage tab, see the Workbench User Guide.
The Server Manager manages and monitors the OpenROAD Server. The Server Manager provides an intuitive graphical user interface (GUI) for managing the installation.
Note:
• The interface was formerly a separate application named the Visual OpenROAD Server Administrator (Visual OSA), but its functionality is now provided on the Server Manager portlet of the OpenROAD Workbench Manage tab.
• Using the Server Manager, whole installations or individual application instances can be enabled, disabled, and replaced quickly.
Each OpenROAD Server installation has one OpenROAD Name Server. A Name Server is an OpenROAD Server application used by clients to connect to an application by name rather than by hard-coded connection parameters. It is responsible for storage and retrieval of all OpenROAD Server configuration data in the installation's registry. Multiple applications can be registered with one or more OpenROAD Name Servers to provide connection load balancing across processes within a given machine and across processes on different installations.
You can drill down into a particular application to monitor it. The application can be started and stopped, and individual user sessions can be monitored and traced. Each application's callable interface can also be explored dynamically using the Server Manager meta data interface.
The Server Manager also serves as a production system housekeeping console, invoking garbage collection and expired session timeouts within each application and freeing up memory used by stale objects where appropriate. Application registrations can be configured to auto-suspend on connection failure. (At least one instance of the Server Manager must be running for these functions to be operational.)