Abstract:
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.
Abstract:
Data characterizing a source computing environment having at least one hardware resource and at least one workload is obtained, as is a specification of a target computing environment to which the at least one workload is to be migrated in a migration. Based on the data characterizing the source computing environment and the specification of the target computing environment, the migration is categorized into one of a plurality of categories; and the migration is specified in accordance with a migration technique selected based on the categorizing step. Techniques to identify suitable migration candidates are also provided.
Abstract:
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.
Abstract:
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.
Abstract:
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.
Abstract:
A system for proving ownership of digital media works. Proof of ownership of such type of work is provided by a protocol for registering a work with a registration center thus providing the rightful owner or copyright holder of the work with an ownership certificate. There is also provided a protocol for proving to another party who is a prospective buyer or licensee, that an ownership claim is correct and valid by providing the ownership certificate when required. Another protocol is utilized for showing to a third party, a prospective buyer or licensee, that a second party has correctly obtained the corresponding work from the rightful copyright owner.
Abstract:
Techniques for unstacking software components are provided. The techniques include discovering a plurality of software components and one or more dependencies between the software components in a computer system, designing a plurality of unstacking options for unstacking said components, and selecting one of said unstacking options to unstack said components.
Abstract:
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.
Abstract:
Infrastructures of a plurality of existing applications of an entity are analyzed to identify at least one of the infrastructures of the plurality of existing applications which includes existing substructures enabling replication of individual parts via an existing replication mechanism. The at least one of the infrastructures is selected for migration to a cloud. The cloud includes at least one of an infrastructure as a service cloud and a platform as a service cloud. The existing substructures of the at least one of the infrastructures are migrated to the cloud, without application-level change. A business agility component is assembled and is configured to control extending and shrinking resources of the cloud that are devoted to the at least one of the infrastructures. The resources of the cloud that are devoted to the at least one of the infrastructures are extended and shrunk, using the business agility component.
Abstract:
An application resource manager obtains a projection of upcoming demand for an application that runs on a cloud. The cloud includes at least one of an infrastructure as a service cloud and a platform as a service cloud. The application resource manager determines, based on the projection, that resources of the cloud that are devoted to the application need to be one of extended and shrunken. One of extending and shrinking the resources of the cloud that are devoted to the application is carried out in response to the determining.