International Business Machines Corporation

Other

Paul Joseph Reder

William Arpad Nagy

Wade C Allen

Jeremy P Goodwin

Douglas Toltzman

Robert Louis Nielsen

Mark Clarence Zelek

Lucas Kalisz

Brian Kalisz

Carole Ameila McCallum

James L Panian

An approach is provided in which a mobile device collects serviceability data from applications executing on the mobile device based upon one or more serviceability state changes provided by a server. The mobile device filters the collected serviceability data according to one or more collection filter rules provided by the server and, in turn, sends the filtered serviceability data to the server accordingly.

Customizable serviceability mechanism

A large cup and small cup are provided which are attachable together. With an upright attachment the large cup nests within a reservoir of the small cup. With an inverted attachment, the small cup has a base which can friction fit against a lower end of the large cup. The small cup includes structures such as a skirt and shelf which can exhibit a friction fit with a foot on the lower end of the large cup to facilitate the inverted attachment of the small cup to the large cup. A recess in the base of the small cup exhibits a friction fit with the foot to facilitate upright attachment when the large cup is nested into the small cup. In an alternative embodiment a fastener is provided including posts and slots in the small cup and large cup to couple the cups together when nested together.

Cup assembly

A method of customizing a graphical user interface (GUI) having one or more command structures (such as toolbars, pull-down menus, or status bars), by dynamically modifying the command structure in response to direct manipulation of the command structure using a graphical pointer of the GUI controlled by a pointing device (e.g., mouse). The structures may be modified using a direct manipulation &ldquo;drag-and-drop&rdquo; procedure. A command item can be dragged from a first location within a command structure to a second location within the same command structure, simply moving the position of the item within that structure. The command item can also be dragged from a first location within a command structure to a second location outside of the command structure, such as to a trash bin provided by the GUI (for deletion of the item), or to a second command structure (for moving or copying the item, e.g., from a toolbar to a pull-down menu). Customized interfaces can be saved and maintained with password protection, allowing a system administrator to lock an interface.

Flexible mouse-driven method of user interface

A method and system for processing an event notification generated by a proxy managed object in a management system, where the management system includes at least one manager and at least one agent. The agent includes a proxy agent coordinator, at least one proxy agent containing one or more event forwarding discriminators, and at least one proxy managed object. The method includes the steps of providing a proxy agent identifier in the notification generated by the proxy managed object, comparing the proxy agent identifier in the notification to an identifier stored in the event forwarding discriminator, and processing the notification if the identifier in the notification matches the identifier stored in the event forwarding discriminator. A set of event forwarding discriminators on one proxy agent can be distinguished from other sets of event forwarding discriminators on other proxy agents via a unique proxy agent identifier for each proxy agent which is stored in the proxy managed object and the event forwarding discriminators, and the unique proxy agent identifier is forwarded in any notification from the proxy managed object to all of the event forwarding discriminators in the system. This method and system is transparent to the manager.

Transparent proxying of event forwarding discriminators

In an Open System Interconnection (OSI) environment, an agent Common Management Information Protocol (CMIP) platform maintains an up to date tree of all of the Managed Object Instances (MOIs), in order to perform scoping functions. The agent platform receives a message from an OSI manager which includes a base MOI and levels below the base MOI to receive the message. The agent platform recurses through the tree below the base MOI to determine which MOIs should receive the message. If the message is delete, the children of MOIs to be deleted are also deleted. The children of undeletable MOIs are not deleted. A current, accurate tree is maintained by the agent platform, which can register a new MOI in the tree when a valid request is received from the MOI or the manager. The agent platform can also deregister an MOI upon valid request from the agent associated with the platform.

Object independent scoping in an open system interconnection system

Information on GDMO managed objects, including class hierarchy and the name binding templates, is compiled into a naming table. This naming table is built from an inheritance table and the name binding template information. The inheritance table indicates the inheritance hierarchy of the managed object classes. The compiler builds the inheritance table as a square matrix with a row and column for each class, and the classes arranged in an ordered list from highest to lowest in hierarchy. The compiler enters a one at each position in the inheritance table to indicate that the managed object class in the row inherits from the managed class in the column. With the inheritance table as a ready reference, the compiler builds the naming table from the name binding templates available as listed in the GDMO source files. The naming table is a square matrix identical to the inheritance table except the entries in the naming table are not ones and zeros. Instead, entries in the naming table are lists of name binding templates that may be used to instantiate a managed object instance in the row class under a managed object instance in the column class.

Compilation of information contained in GDMO name bindings

Managed Object Instances (MOIs) in a network of OSI computing systems are created, or deleted, without disrupting their interaction with other managed object instances. This is accomplished by a multi-phase commit process operation where in the first phase, a create or delete request is verified, and the CMIP platform places the created or deleted MOI on a pending list in the CMIP platform, along with information identifying the location of the MOI in a hierarchy of MOIs. In the second phase, the object being created or deleted is asked to accept, or reject, the request. The object responds saying that it accepts or rejects the request. If the request is acceptable, the CMIP platform finishes the object's connection to the tree hierarchy, or disconnects the object from the tree. Then the CMIP platform sends back a message to the object to acknowledge the creation of the object, or to tell the object to delete itself. Finally, the CMIP platform sends a request completion message to the manager.

Multi-phase commit processing for creation and deletion of managed

A new event forwarding discriminator (EFD) EFD named the persistent/impervious event forwarding discriminator (PI EFD) is described herein. The PI EFD is monitored by the agent infrastructure in such a way that if the agent goes down, and thus the PI EFD goes down, the agent rebuilds or restores the PI EFD with all its attributes. The PI EFD immediately creates an event notification indicating a create PI EFD event has occurred. This event notification is of the type passed by the PI EFD to the manager. The manager then knows the poll its other EFDs at the agent and recreate them as necessary. To foil rogue managers, the PI EFD can not be deleted by other managers. Also, the PI EFD has limited attributes that can be changed. A rogue manager can only add himself to the destination list; it can not otherwise change the attributes of the PI EFD.

Growing community of inventors

Durham, NC, United States of America

Paul Joseph Reder