Abstract: A technique to generically manage extensible correlation data is provided for correlating a series of events. The technique employs a global unique identifier (GUID) for identifying an event and uses the GUID as a key to associate one or more extensible correlators of correlation data. A transport correlator may be configured to transport the GUID for associating with a GUID of a second event such that a small and fixed amount of data is passed by the communications layer providing the transport, minimally impacting communications. An arbitrary amount of data may be logged and keyed with the GUID, providing optimization and flexibility.

Abstract: A method, system, and computer usable program product for discovering an equipment power connection relationship between an equipment and an electrical power outlet. A workload executing on the equipment is monitored for a period resulting in monitoring data. The Metering data associated with a first power outlet in a plurality of power outlets is searched, the metering data representing electrical power drawn from a power outlet over the period. A determination is made whether the monitoring data matches with the metering data associated with the first power outlet. If a match is determined, a relationship is identified between the equipment and the first power outlet, whereby the first power outlet is known to supply electrical power to the equipment.

Abstract: An approach is provided that gathers observational traffic data at traffic controller nodes. Each of the traffic controller nodes communicates observational traffic data to other traffic controller nodes via a network. The traffic controller nodes negotiate traffic control parameters. The negotiating process receives timing proposals from the other traffic controller nodes included in the related set. The nodes analyze the proposed timings based on the traffic controller's gathered observational traffic data. The traffic controller node prepares responses in response to the analysis. The traffic controller node sends the negotiation responses to the other traffic controller nodes. The traffic controller node also adjusts its traffic control parameters that control the node's cycle times based on the analysis.

Abstract: An approach is provided that gathers observational traffic data at traffic controller nodes. Each of the traffic controller nodes communicates observational traffic data other traffic controller nodes via a network. The traffic controller nodes negotiate traffic control parameters. The negotiating process receives timing proposals from the other traffic controller nodes included in the related set. The nodes analyze the proposed timings based on the traffic controller's gathered observational traffic data. The traffic controller node prepares responses in response to the analysis. The traffic controller node sends the negotiation responses to the other traffic controller nodes. The traffic controller node also adjusts its traffic control parameters that control the node's cycle times based on the analysis.

Abstract: A method, system, and computer usable program product for discovering an equipment power connection relationship between an equipment and an electrical power outlet. A workload executing on the equipment is monitored for a period resulting in monitoring data. The Metering data associated with a first power outlet in a plurality of power outlets is searched, the metering data representing electrical power drawn from a power outlet over the period. A determination is made whether the monitoring data matches with the metering data associated with the first power outlet. If a match is determined, a relationship is identified between the equipment and the first power outlet, whereby the first power outlet is known to supply electrical power to the equipment.

Abstract: Provided are a method, a system, an article of manufacture, and a computer program product, wherein a first indicator is stored for a first entity, and wherein the first indicator identifies groups to which the first entity belongs and operations associated with the groups. The first entity receives a second indicator from a second entity, wherein the second indicator indicates privileges granted to the second entity for at least one operation on at least one group. A determination is made locally by the first entity, whether an operation requested by the second entity is to be executed by the first entity, based on a comparison of the second indicator to the first indicator.

Abstract: A technique to generically manage extensible correlation data is provided for correlating a series of events. The technique employs a global unique identifier (GUID) for identifying an event and uses the GUID as a key to associate one or more extensible correlators of correlation data. A transport correlator may be configured to transport the GUID for associating with a GUID of a second event such that a small and fixed amount of data is passed by the communications layer providing the transport, minimally impacting communications. An arbitrary amount of data may be logged and keyed with the GUID, providing optimization and flexibility.

Abstract: A computer implemented method for managing IM presence based on task context, comprising storing group affiliations for a requesting IM user and a target IM user. A request from the requesting IM user is received for the target IM user's status. The requesting IM user's group affiliation is determined. The target IM user's status relationship associated with the requesting IM user's group affiliation is determined. The status relationship for the target IM user is returned to the requesting IM user. Communication from the requesting IM user is forwarded to a predefined reroute destination if the target IM user has defined the reroute destination for communication originating from the requesting IM user's group affiliation.

Abstract: A technique to generically manage extensible correlation data is provided for correlating a series of events. The technique employs a global unique identifier (GUID) for identifying an event and uses the GUID as a key to associate one or more extensible correlators of correlation data. A transport correlator may be configured to transport the GUID for associating with a GUID of a second event such that a small and fixed amount of data is passed by the communications layer providing the transport, minimally impacting communications. An arbitrary amount of data may be logged and keyed with the GUID, providing optimization and flexibility.

Abstract: Calibration factors determine how topograpy components are designed and built in order to support the management philosophies and methodologies. A marketing analysis may be used to identify the calibration factors that are needed to support a large market. In this manner, many calibration factors may be applied to a single topography requirement so that multiple operating environments and multiple management philosophies are supported by the topography. The components are stored in a component library and calibration factors corresponding to the components are stored in a data store. A customer's management philosophy, methodology, and operating environments are compared with the component metadata in order to identify suitable topography components which are installed on client computer systems to form to topography. Topography-neutral application components are adapted for installation on any topography regardless of the customer's management characteristics and operating environments.

Abstract: A system and method for developing topography based management systems is presented. A software system is designed using a layered approach that provides a topography that is suitable to a particular management philosophy or particular customer requirements. The topography can be viewed as a fabric that provides an infrastructure that supports the customer's management philosophy and other requirements. The topography addresses deployment mechanisms, such as interfaces between applications and users, security infrastructure, such as what control is asserted and maintained for the topography, component interaction defining how components installed on the topography interact with one another, and operation conduits that determine where and how processing is performed within the infrastructure. These same capabilities are addressed by other topographies that are developed. Common topography-neutral application components are designed and built to be installed on any topography.

Abstract: As a solution to the problem of distributed knowledge of data object definitions, data object definitions are removed from the source code. A Meta Data Service is created and made available on a network which knows the definitions of all of the objects that are used by applications that are designed to use the Meta Data Service. When an object is created, the Meta Data Service creates and stores a meta definition for the object. Data objects are passed over a network in a “soft” format. Applications within a distributed data processing system are designed in such a manner such that, at any stage of object processing, an application does not assume to understand the definition or structure of an object, nor is an application hard-coded with the object definitions. At each stage, an application queries the Meta Data Service for the meta definition of the object before proceeding with the processing of an object.

Abstract: A technique to generically manage extensible correlation data is provided for correlating a series of events. The technique employs a global unique identifier (GUID) for identifying an event and uses the GUID as a key to associate one or more extensible correlators of correlation data. A transport correlator may be configured to transport the GUID for associating with a GUID of a second event such that a small and fixed amount of data is passed by the communications layer providing the transport, minimally impacting communications. An arbitrary amount of data may be logged and keyed with the GUID, providing optimization and flexibility.

Abstract: Calibration factors determine how topograpy components are designed and built in order to support the management philosophies and methodologies. A marketing analysis may be used to identify the calibration factors that are needed to support a large market. In this manner, many calibration factors may be applied to a single topography requirement so that multiple operating environments and multiple management philosophies are supported by the topography. The components are stored in a component library and calibration factors corresponding to the components are stored in a data store. A customer's management philosophy, methodology, and operating environments are compared with the component metadata in order to identify suitable topography components which are installed on client computer systems to form to topography. Topography-neutral application components are adapted for installation on any topography regardless of the customer's management characteristics and operating environments.

Abstract: A system and method for developing topography based management systems is presented. A software system is designed using a layered approach that provides a topography that is suitable to a particular management philosophy or particular customer requirements. The topography can be viewed as a fabric that provides an infrastructure that supports the customer's management philosophy and other requirements. The topography addresses deployment mechanisms, such as interfaces between applications and users, security infrastructure, such as what control is asserted and maintained for the topography, component interaction defining how components installed on the topography interact with one another, and operation conduits that determine where and how processing is performed within the infrastructure. These same capabilities are addressed by other topographies that are developed. Common topography-neutral application components are designed and built to be installed on any topography.

Abstract: An adaptive learning system and method. This method begins when a problem description provided by the user is received. This problem description may include non-tokenized text. The description is then searched character-by-character against a unique keyword data structure for any user-defined keywords. During this matching process, the routine examines each character in the description and compares it to the keywords in the data structure. Once all keywords are identified, the routine generates a set of solutions associated with at least one of the matching keywords. These solutions are then ranked, for example, based on how many times a respective solution has been used (to solve the problem previously) or how may matching keywords are associated with a respective solution.

Abstract: A method for searching a non-tokenized text string for matches against a keyword data structure organized as a set of one or more keyword objects. The method begins by (a) indexing into the keyword data structure using a character in the non-tokenized text string. Preferably, the character is a Unicode value. The routine then continues by (b) comparing a portion of the non-tokenized text string to a keyword object. If the portion of the non-tokenized text string matches the keyword object, the routine saves the keyword object in a match list. If, however, the portion of the non-tokenized text string does not match the keyword object and there are no other keyword objects that share a root with the non-matched keyword object, the routine repeats step (a) with a new character. These steps are then repeated until all characters in the non-tokenized text string have been analyzed against the keyword data structure.