Abstract: An approach is provided for managing resiliency of an application provided by a first service provider (SP). A fail condition indicating an outage of a first service of the first SP is detected. Based on a topology mapping the first SP to a second SP and the first service to a second service of the second SP, a first API provided by the first SP is determined to have provided the first service prior to the fail condition, and a second API provided by the second SP is determined to provide the second service. The first API is disabled and the second API is activated, thereby continuing to provide a functionality of the application that had been provided by the first service prior to the fail condition being detected, even though the first SP is experiencing the fail condition.

Abstract: An approach is provided for managing resiliency of an application provided by a first service provider (SP). A fail condition indicating an outage of a first service of the first SP is detected. Based on a topology mapping the first SP to a second SP and the first service to a second service of the second SP, a first API provided by the first SP is determined to have provided the first service prior to the fail condition, and a second API provided by the second SP is determined to provide the second service. The first API is disabled and the second API is activated, thereby continuing to provide a functionality of the application that had been provided by the first service prior to the fail condition being detected, even though the first SP is experiencing the fail condition.

Abstract: An approach is provided for managing resiliency of an application. Based on information specifying services provided by service providers (SPs) which is stored in a configuration management database, a topology mapping a first service provided by a first SP to a second service provided by a second SP is generated. Each of the first and second services provides a functionality of the application. A fail condition of the first SP is detected. Based on the topology, a first API provided by the first SP is determined to have provided the first service prior to the fail condition, and a second API provided by the second SP is determined to provide the second service. The first API provided by the first SP is disabled and the second API is activated, thereby continuing to provide the functionality of the application even though the first SP is experiencing the fail condition.

Abstract: An approach is provided for managing resiliency of an application. Based on information specifying services provided by service providers (SPs) which is stored in a configuration management database, a topology mapping a first service provided by a first SP to a second service provided by a second SP is generated. Each of the first and second services provides a functionality of the application. A fail condition of the first SP is detected. Based on the topology, a first API provided by the first SP is determined to have provided the first service prior to the fail condition, and a second API provided by the second SP is determined to provide the second service. The first API provided by the first SP is disabled and the second API is activated, thereby continuing to provide the functionality of the application even though the first SP is experiencing the fail condition.

Abstract: In general, embodiments of the present invention provide an approach for evaluating a computer environment. Specifically, actual deployed components of the computer systems are discovered and cross-referenced against a pre-determined functional architecture to produce a new physical pattern model to determine whether critical functions within the computer environment are not implemented or whether deployed components within the computer environment are over or under capacity.

Abstract: In a method for managing assets in a computing environment, one or more processors identifying a first memory page in a listing of memory pages in a server. The method further includes one or more processors identifying a set of information that is associated with a life span of an asset, wherein the asset is a hardware asset or a software asset. The method further includes one or more processors determining a weighted rating for the asset based on the identified set of information that is associated with the life span of the asset. The method further includes one or more processors determining a replacement age for the asset based on the determined weighted rating for the asset. The method further includes one or more processors determining whether to provide an alert indicating information associated with replacing the asset.