Abstract: Roll back strategies for database deadlock resolution are customized by identifying a first transaction to a database, identifying a second transaction to the database and detecting a deadlock between the first and second transactions with respect to the database. The deadlock is resolved based upon a predetermined roll back strategy associated with at least one of the first or second transactions to identify a select one of the first and second transactions for roll back and a request is conveyed to roll back the selected one of the first and second transactions, wherein the preferred transaction is allowed to continue processing.

Abstract: Systems, methods and computer program products are provided for identifying a first component on a first server and a second component on a second server for co-location, where the first and second servers are within a domain boundary; inspecting available server resources within the domain boundary; determining a select server in the domain boundary for co-location based upon the inspection of available server resources; and autonomically co-locating the first and second components to the select server.

Abstract: Systems, methods and computer program products are provided for reducing overhead in component interactions comprising monitoring interactions between components residing within a domain boundary; storing data indicative of the interactions; analyzing the data to determine whether there is a first component on a first server and a second component on a second server within the domain boundary that are coupled and dislocated that should be co-located; evaluating available server resources; determining whether the first and second components can be co-located based upon the evaluation of available server resources; and conveying a request to co-locate the first and second components if it is determined that the first and second components can be co-located.

Abstract: Roll back strategies for database deadlock resolution are customized by identifying a first transaction to a database, identifying a second transaction to the database and detecting a deadlock between the first and second transactions with respect to the database. The deadlock is resolved based upon a predetermined roll back strategy associated with at least one of the first or second transactions to identify a select one of the first and second transactions for roll back and a request is conveyed to roll back the selected one of the first and second transactions, wherein the preferred transaction is allowed to continue processing.

Abstract: Systems, methods and computer program products are provided for reducing overhead in component interactions comprising monitoring interactions between components residing within a domain boundary; storing data indicative of the interactions; analyzing the data to determine whether there is a first component on a first server and a second component on a second server within the domain boundary that are coupled and dislocated that should be co-located; evaluating available server resources; determining whether the first and second components can be co-located based upon the evaluation of available server resources; and conveying a request to co-locate the first and second components if it is determined that the first and second components can be co-located.

Abstract: Systems, methods and computer program products are provided for identifying a first component on a first server and a second component on a second server for co-location, where the first and second servers are within a domain boundary; inspecting available server resources within the domain boundary; determining a select server in the domain boundary for co-location based upon the inspection of available server resources; and autonomically co-locating the first and second components to the select server.