Determining application composition and ownership
US-9575979-B1 · Feb 21, 2017 · US
US11194558B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-11194558-B2 |
| Application number | US-201715725477-A |
| Country | US |
| Kind code | B2 |
| Filing date | Oct 5, 2017 |
| Priority date | Oct 14, 2016 |
| Publication date | Dec 7, 2021 |
| Grant date | Dec 7, 2021 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
An application-centric modernization and migration (AMM) architecture delivers AMM as a service to enterprises to automate migrating applications to new environments. In this regard, the architecture implements data migration functionality in concert with application code migration, environment provisioning, and post-migration configuration. The joint migration of application data and application code effectively provides a complete migration of an application. The architecture may also define and deliver a GUI portal through which an application owner provides application-specific metadata to drive the AMM.
Opening claim text (preview).
What is claimed is: 1. A method comprising: defining an application service center interface; delivering the application service center interface through a communication interface to an application owner; registering a specific application through the application service center interface, including: responsive to operator input at the application service center interface, identifying an application database required for execution of the specific application, the operator input including a request to register the application database for the specific application; identifying a source environment in which the specific application currently runs; assigning the specific application to an application-specific metadata model; adding, into the application-specific metadata model, application database identification metadata and application database location metadata characterizing the application database; and adding, into the application-specific metadata model, source environment metadata that characterizes the source environment in which the specific application currently runs; and initiating migration of the specific application through the application service center interface, including: requesting deployment of a target environment for the specific application; recognizing that the application database is required for execution of the specific application; and controlling migration of the application database into the target environment; and controlling migration of the specific application into the target environment by: generating multiple different hardware mappings to the target environment for a hardware component accessible within the source environment; and providing individual ones of the multiple different hardware mappings to respective accept-mapping selectors within the application service center interface to facilitate an operator selection among the multiple different hardware mappings via an input device, each of the accept-mapping selectors detailing a different hardware configuration, each of the different hardware mappings including: a specific number of processor cores; a specific amount of disk space; and a specific amount of Random Access Memory (RAM); for each hardware component in the individual ones of the multiple different hardware mappings, providing a listing of alternate mappings for the hardware component for display at a time of selection of a graphical user interface (GUI) element within the application service center interface; providing a listing of pending items to a pending items panel in the application service center interface, the pending items including instances of hardware components for which provisioning is currently pending; and for each of the pending items, providing a change request indicator displayed separately from the listing, the change request indicator configured to open a detail view responsive to operator input, the detail view including an option to request a change to the respective pending item, the option to request the change including an option to request to change: a priority of the pending item; a requestor name for the pending item; a risk level for the pending item; an impact level for the pending item; a configuration item for the pending item; a category for the pending item; a state for the pending item; an assigned group for the pending item; an authorization approval of the pending item; and a description of the pending item. 2. The method of claim 1 , further comprising: receiving, through the application service center interface, an identification of the target environment. 3. The method of claim 1 , further comprising: executing mapping rules to determine the target environment from the source environment. 4. The method of claim 1 , where: the source environment is a first virtualized environment; and the target environment is a second virtualized environment. 5. The method of claim 1 , where: the source environment is a non-virtualized environment; and the target environment is a virtualized environment. 6. The method of claim 1 , where: controlling migration of the application database comprises issuing provisioning instructions for instantiating the application database in the target environment. 7. The method of claim 1 , where: controlling migration of the application database comprises issuing provisioning instructions for instantiating the application database into the target environment as a virtualized application database. 8. The method of claim 1 , where: controlling migration of the application database comprises identifying specific data fields in the application database as masked data fields; and preventing data entries in the masked data fields from appearing in the application database in the target environment by clearing the masked entries during transfer to the target environment. 9. The method of claim 1 , further comprising: executing post-migration configuration on the specific application in the target environment. 10. The method of claim 9 , where: the executing comprises: reconfiguring the specific application to access the application database in the target environment. 11. A system comprising: machine interface circuitry defining an application service center interface; a communication interface circuitry configured to deliver the application service center interface to an application owner; and application configuration circuitry configured to: register a specific application through the application service center interface by: responsive to operator input at the application service center interface, identifying an application database required for execution of the specific application, the operator input including a request to register the application database for the specific application; identifying a source environment in which the specific application currently runs; assigning the specific application to an application-specific metadata model; adding, into the application-specific metadata model, application database identification metadata and application database location metadata characterizing the application database; and adding, into the application-specific metadata model, source environment metadata that characterizes the source environment in which the specific application currently runs; and initiate migration of the specific application through the application service center interface by: requesting deployment of a target environment for the specific application; recognizing that the specific application relies on the application database during execution of the specific application; and controlling migration of the application database into the target environment; and controlling migration of the specific application into the target environment by: generating multiple different hardware mappings to the target environment for a hardware component accessible within the source environment; providing individual ones of the multiple different hardware mappings to respective accept-mapping selectors within the application service center interface to facilitate an operator selection among the multiple different hardware mappings via an input device, each of the accept-mapping selectors detailing a different hardware configuration, each of the different hardware mappings including: a specific number of processor cores; a specific amount of disk space; and a specific amount of Random Access Memory (RAM); for each hardware component in the individual ones of the multiple different hardware mappings, providing a listing of alternate mappings for the hardware component for display at a
resumption being on a different machine, e.g. task migration, virtual machine migration (G06F9/5088 takes precedence) · CPC title
Software deployment · CPC title
Retargetable · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.