Computing instance migration
US-10382408-B1 · Aug 13, 2019 · US
US11514017B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-11514017-B2 |
| Application number | US-202016983907-A |
| Country | US |
| Kind code | B2 |
| Filing date | Aug 3, 2020 |
| Priority date | Aug 2, 2019 |
| Publication date | Nov 29, 2022 |
| Grant date | Nov 29, 2022 |
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.
Systems and methods for provisioning a new secondary IdentityIQ instance to an existing IdentityIQ instance are disclosed. In one embodiment, a method may include: receiving a request to provision the new secondary IdentityIQ instance; creating a primary IdentityIQ instance for the existing IdentityIQ instance and the new secondary IdentityIQ instance; aggregating data from the existing IdentityIQ instance to the primary IdentityIQ instance; deploying an event handler to the primary IdentityIQ instance to handle incoming requests for the existing IdentityIQ instance; changing a reconciliation process and an audit process from the existing IdentityIQ instance to the primary IdentityIQ instance thereby changing the existing IdentityIQ instance to the secondary IdentityIQ instance for the primary IdentityIQ instance; deploying the new secondary IdentityIQ instance to the primary IdentityIQ instance; and deploying at least one application to the new secondary IdentityIQ instance based on an operation processed by the new secondary IdentityIQ instance.
Opening claim text (preview).
What is claimed is: 1. A method for provisioning an existing IdentityIQ instance with a new secondary IdentityIQ instance, comprising: receiving a request to provision the new secondary IdentityIQ instance; creating a primary IdentityIQ instance for the existing IdentityIQ instance and the new secondary IdentityIQ instance; aggregating data from the existing IdentityIQ instance to the primary IdentityIQ instance; deploying an event handler to the primary IdentityIQ instance to handle incoming requests for the existing IdentityIQ instance; changing a reconciliation process and an audit process from the existing IdentityIQ instance to the primary IdentityIQ instance thereby changing the existing IdentityIQ instance to the secondary IdentityIQ instance for the primary IdentityIQ instance; deploying the new secondary IdentityIQ instance to the primary IdentityIQ instance; and deploying at least one application to the new secondary IdentityIQ instance based on an operation processed by the new secondary IdentityIQ instance. 2. The method of claim 1 , wherein the request to provision the new secondary IdentityIQ instance is received by the existing IdentityIQ instance. 3. The method of claim 1 , wherein the request to provision the new secondary IdentityIQ instance comprises an identification of a target endpoint type for the new secondary IdentityIQ instance. 4. The method of claim 1 , wherein the target endpoint type comprises one of a mainframe, infrastructure as a service, a human, and a non-human. 5. The method of claim 1 , further comprising: verifying that hardware to support the new secondary IdentityIQ instance is available. 6. The method of claim 1 , wherein the data aggregated from the existing IdentityIQ instance comprises data from the existing IdentityIQ instance's IdentityIQ database. 7. The method of claim 1 , wherein the request handler processes requests with an access catalog. 8. The method of claim 1 , wherein the step of deploying the new secondary IdentityIQ instance comprises updating logic the primary IdentityIQ instance is updated to recognize the target endpoints for the new secondary IdentityIQ instance. 9. The method of claim 3 , wherein the at least one application that is deployed to the second IdentityIQ instance is associated with the target endpoint type for the new secondary IdentityIQ instance. 10. A system for provisioning an existing instance with a new secondary instance, comprising: an existing IdentityIQ instance; a primary IdentityIQ instance; and a new secondary IdentityIQ instance; wherein: the primary IdentityIQ instance aggregates data from the existing IdentityIQ instance; the primary IdentityIQ instance's event handler is updated to handle incoming requests for the existing IdentityIQ instance; the primary IdentityIQ instances' reconciliation process and audit process are changed from the existing IdentityIQ instance to the primary IdentityIQ instance; and at least one application is deployed to the new secondary IdentityIQ instance based on an operation processed by the new secondary IdentityIQ instance. 11. The system of claim 10 , wherein the request to provision the new secondary IdentityIQ instance is received by the existing IdentityIQ instance. 12. The system of claim 10 , wherein the request to provision the new secondary IdentityIQ instance comprises an identification of a target endpoint type for the new secondary IdentityIQ instance. 13. The system of claim 10 , wherein the target endpoint type comprises one of a mainframe, infrastructure as a service, a human, and a non-human. 14. The system of claim 10 , further comprising a host program or application that verifies that hardware to support the new secondary IdentityIQ instance is available. 15. The system of claim 10 , wherein the data aggregated from the existing IdentityIQ instance comprises data from the existing IdentityIQ instance's IdentityIQ database. 16. The system of claim 10 , wherein the request handler processes requests with an access catalog. 17. The system of claim 10 , wherein logic in the primary IdentityIQ instance is updated to recognize the target endpoints for the new secondary IdentityIQ instance. 18. The system of claim 12 , wherein the at least one application that is deployed to the second IdentityIQ instance is associated with the target endpoint type for the new secondary IdentityIQ instance.
Hypervisor-specific management and integration aspects · CPC title
Task life-cycle, e.g. stopping, restarting, resuming execution (G06F9/4881 takes precedence) · CPC title
Aggregation; Duplicate elimination · CPC title
Creating, deleting, cloning virtual machine instances · CPC title
involving the movement of software or configuration parameters (network booting or remote initial program loading [RIPL] G06F9/4416) · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.