Harigovind V Ramasamy

8583709, Nov 12, 2013

Mar 18, 2010

12/726857

Nikolai A. Joukov - Thornwood NY,
Birgit Pfitzmann - Valhalla NY,
Shaya Potter - New York NY,
Harigovind V. Ramasamy - Tarrytown NY,

International Business Machines Corporation - Armonk NY

G06F 17/30

707822

A file system interface is simulated out of at least a portion of a dormant computer system. File-based discovery is performed on the simulated file system interface to obtain a detailed inventory of at least the portion of the dormant computer system. The detailed inventory includes one or more of software profiles of at least the portion of the dormant computer system, software instances of at least the portion of the dormant computer system, services of at least the portion of the dormant computer system, and data objects used by the services.

2011013, Jun 2, 2011

Dec 1, 2009

12/628420

Birgit Monika Pfitzmann - Hawthorne NY,
Harigovind Venkatraj Ramasamy - Hawthorne NY,
Cheng-Lin Tsao - Atlanta GA,

INTERNATIONAL BUSINESS MACHINES CORPORATION - ARMONK NY

G06F 17/00

726 1

A system and method for discovering security classifications of network areas includes representing actually allowed network flows and flows permitted by a security policy in a format that enables comparison. The actually allowed network flows and the security policy are provided in a networked computing environment including network areas, wherein each network area is a collection of one or more computing and network devices, and enterprise security policy defines security requirements for security classifications. An assignment of security classifications to network areas is determined by comparing the actually allowed network flows with the flows permitted by the security policy.

2011025, Oct 13, 2011

Apr 13, 2010

12/759356

Nikolai A. Joukov - Thornwood NY,
Matthew A. Markley - Hays KS,
Birgit Pfitzmann - Valhalla NY,
HariGovind V. Ramasamy - Tarrytown NY,

INTERNATIONAL BUSINESS MACHINES CORPORATION - Armonk NY

G06F 9/44

717121, 717120

Component relinking in migrations may include discovering one or more dependencies in one or more components; planning one or more new locations where the one or more components are to be placed; determining relinking needs in the one or more components based on the discovering and the planning; and applying the relinking needs.

2011030, Dec 8, 2011

Jun 3, 2010

12/793202

Kamal Bhattacharya - Gurgaon,
Nikolai A. Joukov - Thornwood NY,
Birgit Pfitzmann - Valhalla NY,
HariGovind V. Ramasamy - Tarrytown NY,

INTERNATIONAL BUSINESS MACHINES CORPORATION - Armonk NY

G06F 15/177
G06F 21/20

726 11, 709221

Automating network reconfiguration such as firewall reconfiguration in migrations may include determining network reconfiguration needs in one or more network functionalities of the target environment based on the discovering; and applying the network reconfiguration needs to the one or more network functionalities in the target environment.

2012015, Jun 14, 2012

Dec 9, 2010

12/964340

Michael M. Behrendt - Randersacker,
Rafah A. Hosn - New York NY,
Ruchi Mahindru - Elmsford NY,
Harigovind V. Ramasamy - Ossining NY,
Soumitra Sarkar - Cary NC,
Mahesh Viswanathan - Yorktown Heights NY,
Norbert G. Vogl - Mahopac NY,

INTERNATIONAL BUSINESS MACHINES CORPORATION - Armonk NY

G06F 11/14

714 39, 714E11142

A scalable and fault tolerant finite state machine engine, for example, for use in an automated incident management system, logs or records data in persistent storage at different points or levels during various internal processing of an event associated with an information technology element, and action taken associated with the event, by executing a finite state machine instance that encodes policies for handling incidents on such types of information technology elements. In the event that the finite state machine engine is shutdown during processing, the finite state machine engine is able to pick up from where it left off when it was shutdown, for each abnormally terminated finite state machine instance, by using the data logged in the persistent storage and determining a point of processing from where it should continue its execution.

2012033, Dec 27, 2012

Sep 5, 2012

13/603879

Michael M. Behrendt - Randersacker,
Rafah A. Hosn - New York NY,
Ruchi Mahindru - Elmsford NY,
Harigovind V. Ramasamy - Ossining NY,
Soumitra Sarkar - Cary NC,
Mahesh Viswanathan - Yorktown Heights NY,
Norbert G. Vogl - Mahopac NY,

International Business Machines Corporation - Armonk NY

G06F 11/14

714 23, 714E11137

A scalable and fault tolerant finite state machine engine, for example, for use in an automated incident management system, logs or records data in persistent storage at different points or levels during various internal processing of an event associated with an information technology element, and action taken associated with the event, by executing a finite state machine instance that encodes policies for handling incidents on such types of information technology elements. In the event that the finite state machine engine is shutdown during processing, the finite state machine engine is able to pick up from where it left off when it was shutdown, for each abnormally terminated finite state machine instance, by using the data logged in the persistent storage and determining a point of processing from where it should continue its execution.

2013028, Oct 24, 2013

Apr 24, 2012

13/454220

Michael M. Behrendt - Randersacker,
Rafah A. Hosn - New York NY,
Ruchi Mahindru - Elmsford NY,
HariGovind V. Ramasamy - Ossining NY,
Soumitra Sarkar - Cary NC,
Mahesh Viswanathan - Yorktown Heights NY,
Norbert G. Vogl - Mahopac NY,

INTERNATIONAL BUSINESS MACHINES CORPORATION - Armonk NY

G06F 11/07

714 2, 714E11023

A mechanism is provided for handling incidents occurring in a managed environment. An incident is detected in a resource in the managed environment. A set of incident handling actions are identified based on incident handling rules for an incident type of the incident. From the set of incident handling actions, one incident handling action is identified to be executed based on a set of impact indicators associated with the set of incident handling rules. The identified incident handling action is then executed to address the failure of the resource.

2013028, Oct 24, 2013

Dec 11, 2012

13/710710

Rafah A. Hosn - New York NY,
Ruchi Mahindru - Elmsford NY,
HariGovind V. Ramasamy - Ossining NY,
Soumitra Sarkar - Cary NC,
Mahesh Viswanathan - Yorktown Heights NY,
Norbert G. Vogl - Mahopac NY,

International Business Machines Corporation - Armonk NY

G06F 11/07

714 2

A mechanism is provided for handling incidents occurring in a managed environment. An incident is detected in a resource in the managed environment. A set of incident handling actions are identified based on incident handling rules for an incident type of the incident. From the set of incident handling actions, one incident handling action is identified to be executed based on a set of impact indicators associated with the set of incident handling rules. The identified incident handling action is then executed to address the failure of the resource.