Error resolution for interactions with user pages
US-2024320079-A1 · Sep 26, 2024 · US
US2017024271A1 · US · A1
| Field | Value |
|---|---|
| Publication number | US-2017024271-A1 |
| Application number | US-201514808234-A |
| Country | US |
| Kind code | A1 |
| Filing date | Jul 24, 2015 |
| Priority date | Jul 24, 2015 |
| Publication date | Jan 26, 2017 |
| Grant date | — |
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.
Methods for notifying, in the event of a power outage, planned maintenance activity, a plurality of stakeholders of an enterprise infrastructure. The enterprise infrastructure may include components and relationships between components. The components may include data centers, data center components, applications, application components, and any other suitable components. The relationships may include relationships between data centers and data center components, relationships between data center components and applications, relationships between applications and application components, relationships between applications and stakeholders. Methods may receive power outage information at an impact notification center. Methods may determine the effect of the power outage on remaining components of the enterprise infrastructure and based on the determination, identify affected components. Methods may notify stakeholders of the power outage, identify service components which might get impacted and perform impact analysis and capacity planning in case of any disaster event where a data center and/or location is impacted.
Opening claim text (preview).
What is claimed is: 1 . A system for notifying, in the event of a power outage, a plurality of stakeholders of an enterprise infrastructure, the system comprising: a region comprising a plurality of data centers, wherein: each data center comprises a plurality of data center components; each data center component is associated with a plurality of application; each application, included in the plurality of applications is associated with at least one data center component; each application, included in the plurality of applications, is associated with a plurality of users, said plurality of users included in the plurality of stakeholders; each user, included in the plurality of users, is associated with at least one application, included in the plurality of applications; each application, included in the plurality of applications, is associated with a plurality of user interfaces (“UIs”); each application, included in the plurality of applications, is associated with a plurality of processes; a server metadata database which receives metadata from each data center component of each data center, the metadata identifies the associated applications; an application metadata database which receive metadata from each application, the metadata identifying the associated UIs, processes, and users; an impact notification center comprising: a reader that reads the metadata from the server metadata database and the metadata from the application metadata database; and a processor that maps the metadata from the server metadata database with the metadata from the application metadata database; when an application, included in the plurality of applications, experiences a power outage, the impact notification center is configured to transmit an impact notification message, said impact notification message which characterizes the effect of the power outage on the remaining components of the system, to the stakeholders which are associated with the application that has experienced the power outage. 2 . The system of claim 1 , wherein the data center components comprise: a plurality of application servers; a plurality of databases; a plurality of publish/subscribe servers; and a plurality of grid engines/schedulers. 3 . The system of claim 1 , wherein when a data center component, included in the plurality of data center components, experiences a data center component power outage, the impact notification center is configured to transmit an impact notification message, said impact notification message which characterizes the effect of the data center component power outage on the remaining components of the system, to the stakeholders which are associated with the data center component that has experienced a data center component power outage. 4 . The system of claim 1 , wherein the characterization includes identifying the date and time that the power outage occurred. 5 . The system of claim 1 , wherein the impact notification message includes a start time of the power outage. 6 . The system of claim 1 , wherein the characterization includes identifying whether the application that experienced a power outage is associated with a production environment or a non-production environment. 7 . The system of claim 1 , wherein the system identifies the component or group of components that experienced a power outage based on the metadata mapping. 8 . The system of claim 7 , wherein the system determines which components were affected by the power outage based on the identification. 9 . A system for notifying, in the event of a scheduled maintenance downtime, a plurality of stakeholders of an enterprise infrastructure, the system comprising: a region comprising a plurality of data centers, wherein: each data center comprises a plurality of data center components; each data center component is associated with a plurality of application; each application, included in the plurality of applications, is associated with at least one data center component; each application, included in the plurality of applications, is associated with a plurality of users, said plurality of users included in the plurality of stakeholders; each user, included in the plurality of users, is associated with at least one application, included in the plurality of applications; each application, included in the plurality of applications, is associated with a plurality of user interfaces (“UI”s); each application, included in the plurality of applications, is associated with a plurality of processes; a server metadata database which receives metadata from each data center component of each data center, the metadata identifies the associated applications; an application metadata database which receive metadata from each application, the metadata identifying the associated UIs, processes, and users; an impact notification center comprising: a receiver that receives the metadata from the server metadata database and the metadata from the application metadata database; and a processor that maps the metadata from the server metadata database with the metadata to the application metadata database; wherein: when an application, included in the plurality of applications, is scheduled to incur maintenance downtime, the impact notification center is configured to transmit an impact notification message, said impact notification message which characterizes the effect of the maintenance downtime on the remaining components of the system, to the stakeholders which are associated with the application that has experienced scheduled maintenance downtime. 10 . The system of claim 9 , wherein the data center components comprise: a plurality of application servers; a plurality of databases; a plurality of publish/subscribe servers; and a plurality of grid engines/schedulers. 11 . The system of claim 9 , wherein the characterization includes identifying the date and time that the maintenance downtime is scheduled. 12 . The system of claim 9 , wherein the impact notification message includes a start time of the maintenance downtime. 13 . The system of claim 9 , wherein the characterization includes identifying whether the application that will incur maintenance downtime is associated with a production environment or a non-production environment. 14 . The system of claim 9 , wherein the system identifies the component or group of components that incurred scheduled maintenance downtime based on the metadata mapping. 15 . The system of claim 7 , wherein the system determines which components will be affected by the maintenance downtime based on the identification. 16 . The system of claim 9 , wherein when a data center component, included in the plurality of data center components, is scheduled to incur a second maintenance downtime, the impact notification center is configured to transmit an impact notification message, said impact notification message which characterizes the effect of the second maintenance downtime on the remaining components of the system, to the stakeholders which are associated with the data center component that has experienced the second scheduled maintenance downtime. 17 . One or more non-transitory computer readable media having code stored thereon which, when executed by a processor on a computer system, performs a method for notifying, in the event of a power outage, a plurality of stakeholders of an enterprise infrastructure, said enterprise infrastructure comprising a plurality of components and a plurality of relationships between the compone
Administration of product repair or maintenance · CPC title
Routing of error reports, e.g. with a specific transmission path or data flow · CPC title
Error or fault detection not based on redundancy (power supply failures G06F1/30; network fault management H04L41/06) · CPC title
Indexing; Data structures therefor; Storage structures · CPC title
Means for error signaling, e.g. using interrupts, exception flags, dedicated error registers · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.