Abstract: A systems management subsystem provides resources for managing components and allows components to be manageable. In particular, state information about managed components is encapsulated into objects that are visible in the global name space. The state of a single component may be partitioned into subcomponents that are stored in separate objects. These objects may, in turn, be encapsulated into a single container object that is associated with the managed component. By placing the state information in the global name space, local processes and remote processes may both gain access to internal state information and properly manage the component.

Abstract: A computer system having a video display runs an operating system that provides a desktop environment to a user and a file system. The desktop environment has associated systems settings that affect the desktop environment. In this method, a first set of values for at least a portion of the system settings are stored in a storage device in a computer network so that the first set of values is visible in the file system. A second set of values, for the same portion of the system settings for which values are stored in the first set of values, is also stored in the storage device such that the second set of values is visible in the file system. In response to a choice by the user between the first set of values and the second set of values, the system settings are updated to have the values specified by the chosen set of values.

Abstract: An event system is provided within an object-oriented environment. The event system informs users and system functions of events within the system. Events may be modeled as objects that are visible within the global namespace. These objects include event source objects and event sink objects. Event source objects generate event reports and event sink objects are the objects that receive reports. Special objects may be incorporated in the system to direct event reports from an event source object to an event sink object.

Abstract: A systems management subsystem provides resources for managing components and allows components to be manageable. In particular, state information about managed components is encapsulated into objects that are visible in the global name space. The state of a single component may be partitioned into subcomponents that are stored in separate objects. These objects may, in turn, be encapsulated into a single container object that is associated with the managed component. By placing the state information in the global name space, local processes and remote processes may both gain access to internal state information and properly manage the component.

Abstract: An event system is provided within an object-oriented environment. The event system informs users and system functions of events within the system. Events may be modeled as objects that are visible within the global namespace. These objects include event source objects and event sink objects. Event source objects generate event reports and event sink objects are the objects that receive reports. Special objects may be incorporated in the system to direct event reports from an event source object to an event sink object.

Abstract: A server of a client/server network uses server processes to access shared server resources in response to service requests from client computers connected to the network. The server uses a measured workload indication to assign a received client service request to a server process. In one embodiment the measured workload indication is determined in response to an input from the server's administrator specifying the number of clients (N) which may request service from the server. Using the number N, the server accesses a predefined table to determine the number of clients that may be assigned to each process. In another embodiment, a busy indicator provides a measured workload indication for each active process. The server uses the busy indicator to assign a new client service request to the least busy process.