Abstract: A first future time occurs sooner than a second future time. The first future time indicates when the first and second future times are to be evaluated. The second future time provides a boundary between schedules occurring sooner and schedules occurring later. A schedule is generated and added to a database stored in a non-volatile storage. The schedule is for executing, in relation to an incident, an incident-handling action corresponding to a condition matching the incident. The schedule has an execution time at which to execute the incident-handling action in relation to the incident. Where the execution time is sooner than the second future time, the schedule is added to a queue stored in a volatile memory. Upon a current time equaling the execution time, the schedule is removed from the queue and correspondingly executing the incident-handling action in relation to the incident.

Abstract: Hotspot identification can include receiving data indicating a plurality of reported events each associated with a respective number of configuration items (CIs) of a plurality of CIs and receiving data indicating a topological dependency of each of the plurality of CIs. Hotspot identification can include assigning a weight to each of the respective number of CIs, assigning a weight to CIs of the plurality of CIs having a topological dependency from the respective number of CIs, and identifying the hotspot having a weight assigned thereto that satisfies a hotspot weight threshold.

Abstract: Hotspot identification can include receiving data indicating a plurality of reported events each associated with a respective number of configuration items (CIs) of a plurality of CIs and receiving data indicating a topological dependency of each of the plurality of CIs. Hotspot identification can include assigning a weight to each of the respective number of CIs, assigning a weight to CIs of the plurality of CIs having a topological dependency from the respective number of CIs, and identifying the hotspot having a weight assigned thereto that satisfies a hotspot weight threshold.

Abstract: A method of generating a configuration file is disclosed. According to an embodiment of the invention, the configuration file specifies how an object of a plurality of objects is to be monitored by an agent of an operational management system. The method comprises the step of providing a data file comprising a plurality of parameter settings for a plurality of parameters used to monitor the plurality of objects of the operational management system. The method in accordance with the invention further comprises the step of retrieving a subset of parameter settings from the plurality of parameter settings, wherein the retrieved subset of parameter settings provides specifications for a subset of parameters of the plurality of parameters, wherein the subset of parameters is used to monitor the object.

Abstract: A first future time occurs sooner than a second future time. The first future time indicates when the first and second future times are to be evaluated. The second future time provides a boundary between schedules occurring sooner and schedules occurring later. A schedule is generated and added to a database stored in a non-volatile storage. The schedule is for executing, in relation to an incident, an incident-handling action corresponding to a condition matching the incident. The schedule has an execution time at which to execute the incident-handling action in relation to the incident. Where the execution time is sooner than the second future time, the schedule is added to a queue stored in a volatile memory. Upon a current time equaling the execution time, the schedule is removed from the queue and correspondingly executing the incident-handling action in relation to the incident.

Abstract: A system is provided for dynamically identifying and correlating network domain events. The system includes a network domain and a plurality of managed objects in the network domain. A management server is in communication with the managed objects. The management server can receive domain events from at least one of the managed objects. A management module on the management server maintains a topology of managed objects in the network domain. A rule knowledge base is in communication with the management server. The rule knowledge base includes correlation rules for identifying and correlating domain events. A correlation module utilizes a processor to correlate the domain events with the topology using the correlation rules to identify an interaction between the managed objects and the domain events.

Abstract: A system is provided for dynamically identifying and correlating network domain events. The system includes a network domain and a plurality of managed objects in the network domain. A management server is in communication with the managed objects. The management server can receive domain events from at least one of the managed objects. A management module on the management server maintains a topology of managed objects in the network domain. A rule knowledge base is in communication with the management server. The rule knowledge base includes correlation rules for identifying and correlating domain events. A correlation module utilizes a processor to correlate the domain events with the topology using the correlation rules to identify an interaction between the managed objects and the domain events.

Abstract: A client-server communication method and system establishes a connection to a server from a client using one of either a first or second request-response protocols. The first and second request-response protocols respectively have first and second sets of start-codes for initiating the establishment of the connection, a common predefined port being used for the first and second request-response protocols. The server receives a request from the client having one start-code of the first and second sets of start-codes, and determines which of the first and second request-response protocols to be used for responding to the client request based on the start-code.

Abstract: A method of mapping status messages of monitored objects to service elements in an IT-infrastructure-management system is provided. The service elements and their dependencies being represented by an element graph having directed links between service elements, thereby defining higher-level and lower-level service elements. The method includes directing a status message to at least one higher-level service element; ascertaining, at the higher-level service element, whether the status message pertains to a lower-level service element connected with the higher-level service element; downwardly propagating of the status message to said lower-level service element in response to a positive outcome in the action of ascertaining.

Abstract: The invention relates to a method of specifying a monitoring criterion for a parameter of an object in an operational management system. The method in accordance with the invention comprises the step of assigning first information to the parameter, wherein the first information is associated with a first priority. In a further step, the first information is employed as monitoring criterion for the parameter if no further information associated with a priority higher than the first priority is assigned to the parameter.

Abstract: A method of generating a configuration file is disclosed. According to an embodiment of the invention, the configuration file specifies how an object of a plurality of objects is to be monitored by an agent of an operational management system. The method comprises the step of providing a data file comprising a plurality of parameter settings for a plurality of parameters used to monitor the plurality of objects of the operational management system. The method in accordance with the invention further comprises the step of retrieving a subset of parameter settings from the plurality of parameter settings, wherein the retrieved subset of parameter settings provides specifications for a subset of parameters of the plurality of parameters, wherein the subset of parameters is used to monitor the object.

Abstract: The invention is directed to a method for monitoring services of an information technology (IT) environment. The method comprises evaluating, by a status engine, the status of a service (superordinate service) that depends on at least one of the statuses of one or more other services (subordinate services) and one or more messages. The messages come from services of the IT environment and affect the status of the superordinate service. The evaluation is performed according to one or more rules. The rules include at least one of: a) a rule that is based on additional attributes of the service other than the status; b) a rule that ignores subordinate services; c) a rule that is defined by a user on the basis of at least one of i) logical and ii) arithmetical operations of the status of subordinate services or of said messages or of said attributes; and d) a rule that is programmed individually by a user.

Abstract: A client-server communication method and system establishes a connection to a server from a client using one of either a first or second request-response protocols. The first and second request-response protocols respectively have first and second sets of start-codes for initiating the establishment of the connection, a common predefined port being used for the first and second request-response protocols. The server receives a request from the client having one start-code of the first and second sets of start-codes, and determines which of the first and second request-response protocols to be used for responding to the client request based on the start-code.

Abstract: A method of mapping status messages of monitored objects to service elements in an IT-infrastructure-management system is provided. The service elements and their dependencies being represented by an element graph having directed links between service elements, thereby defining higher-level and lower-level service elements. The method includes directing a status message to at least one higher-level service element; ascertaining, at the higher-level service element, whether the status message pertains to a lower-level service element connected with the higher-level service element; down-wardly propagating of the status message to said lower-level service element in response to a positive outcome in the action of ascertaining.

Abstract: The invention is directed to a method performed by a service management system for monitoring objects of an IT environment. At least some of the objects and their dependencies are represented in a service model. The method comprises that data relating to an object that is not represented in the service model is automatically processed by the service management system, and when said object is later included in the service model, the results of this processing are available for monitoring the included object. The invention is also directed to a corresponding computer system and a corresponding computer program product.

Abstract: The invention is directed to a method performed by a service management system for monitoring objects of an IT environment. At least some of the objects and their dependencies are represented in a service model. The method comprises that data relating to an object that is not represented in the service model is automatically processed by the service management system, and when said object is later included in the service model, the results of this processing are available for monitoring the included object. The invention is also directed to a corresponding computer system and a corresponding computer program product.

Abstract: The invention is directed to a method for monitoring services of an information technology (IT) environment. The method comprises evaluating, by a status engine, the status of a service (superordinate service) that depends on at least one of the statuses of one or more other services (subordinate services) and one or more messages. The messages come from services of the IT environment and affect the status of the superordinate service. The evaluation is performed according to one or more rules.