Remove backend widget status

guides/common/assembly_disaster-recovery-by-virtualizing-your-projectserver.adoc

@@ -7,5 +7,3 @@ include::modules/ref_prerequisites-disaster-recovery-by-virtualizing-your-projec
 include::modules/proc_preparing-for-disaster-recovery-by-virtualizing-your-projectserver.adoc[leveloffset=+1]
 
 include::modules/proc_recovering-from-disaster-by-restoring-a-vm-snapshot-of-projectserver.adoc[leveloffset=+1]
-
-include::modules/proc_retrieving-status-of-services.adoc[leveloffset=+1]

guides/common/assembly_disaster-recovery-for-active-and-passive-project-server-with-external-storage.adoc

@@ -7,5 +7,3 @@ include::modules/ref_prerequisites-disaster-recovery-with-active-and-passive-pro
 include::modules/proc_preparing-for-disaster-recovery-with-active-and-passive-project-server-with-external-storage.adoc[leveloffset=+1]
 
 include::modules/proc_recovering-from-disaster-with-active-and-passive-project-server-with-external-storage.adoc[leveloffset=+1]
-
-include::modules/proc_retrieving-status-of-services.adoc[leveloffset=+1]

guides/common/assembly_disaster-recovery-with-active-and-passive-project-server-and-backup-and-restore.adoc

@@ -8,6 +8,4 @@ include::modules/proc_preparing-for-disaster-recovery-with-active-and-passive-pr
 
 include::modules/proc_recovering-from-disaster-with-active-and-passive-project-server-and-backup-and-restore.adoc[leveloffset=+1]
 
-include::modules/proc_retrieving-status-of-services.adoc[leveloffset=+1]
-
 include::modules/ref_example-of-a-weekly-full-backup-followed-by-daily-incremental-backups.adoc[leveloffset=+1]

guides/common/assembly_logging-and-reporting-problems.adoc

@@ -40,8 +40,6 @@ include::modules/proc_selective-debugging-with-individual-loggers.adoc[leveloffs
 
 include::modules/ref_overview-of-individual-loggers.adoc[leveloffset=+1]
 
-include::modules/proc_retrieving-status-of-services.adoc[leveloffset=+1]
-
 include::modules/proc_restarting-services.adoc[leveloffset=+1]
 
 include::modules/ref_utilities-for-processing-log-information.adoc[leveloffset=+1]

guides/common/assembly_preparing-for-disaster-recovery-and-recovering-from-data-loss.adoc

@@ -4,6 +4,10 @@ include::modules/con_preparing-for-disaster-recovery-and-recovering-from-data-lo
 
 include::modules/con_overview-of-recommended-disaster-recovery-plans.adoc[leveloffset=+1]
 
+include::modules/proc_retrieving-status-of-services-by-using-web-ui.adoc[leveloffset=+1]
+
+include::modules/proc_retrieving-status-of-services-by-using-cli.adoc[leveloffset=+1]
+
 :parent-context: {context}
 :context: dr-virt
 include::assembly_disaster-recovery-by-virtualizing-your-projectserver.adoc[leveloffset=+1]

guides/common/modules/proc_preparing-for-disaster-recovery-by-virtualizing-your-projectserver.adoc

@@ -25,5 +25,5 @@ While snapshots provide quick recovery points, backing up your snapshots gives y
 . Verify that your hypervisor takes the snapshots according to the schedule that you defined.
 . Use the latest snapshot of your {ProjectServer} and restore it in an isolated environment.
 . To verify that you will be able to restore {Project} services in case of a disaster, assess the functionality of the test {ProjectServer}.
-See xref:Retrieving_the_Status_of_Services_{context}[].
+For more information, see xref:retrieving-the-status-of-services-by-using-web-ui[].
 . Perform these verification checks regularly.

guides/common/modules/proc_preparing-for-disaster-recovery-with-active-and-passive-project-server-and-backup-and-restore.adoc

@@ -46,5 +46,5 @@ Consider how many backups you want to store: Regularly removing outdated backups
 To make sure the active server is inaccessible, you can turn the machine off, halt the virtual machine (VM) if your server runs on a VM, or isolate the machine by using a firewall.
 .. Switch DNS records of the active server with the DNS records of the passive server.
 .. Assess the functionality of the test {ProjectServer}.
-For more information, see xref:Retrieving_the_Status_of_Services_{context}[].
+For more information, see xref:retrieving-the-status-of-services-by-using-web-ui[].
 .. Perform these verification checks regularly.

guides/common/modules/proc_preparing-for-disaster-recovery-with-active-and-passive-project-server-with-external-storage.adoc

@@ -37,7 +37,7 @@ To make sure the active server is inaccessible, you can turn the machine off, ha
 . Switch DNS records of the active server with the DNS records of the passive server.
 . Verify that your passive server can access the data stored on your shared storage.
 . Assess the functionality of the test {ProjectServer}.
-For more information, see xref:Retrieving_the_Status_of_Services_{context}[].
+For more information, see xref:retrieving-the-status-of-services-by-using-web-ui[].
 . Perform these verification checks regularly.
 
 ifdef::satellite[]

guides/common/modules/proc_recovering-from-disaster-by-restoring-a-vm-snapshot-of-projectserver.adoc

@@ -20,4 +20,4 @@ This redirects traffic from the old server to the new server and you will not ne
 
 .Verification
 * Assess the functionality of your restored {ProjectServer}.
-See xref:Retrieving_the_Status_of_Services_{context}[].
+For more information, see xref:retrieving-the-status-of-services-by-using-web-ui[].

guides/common/modules/proc_recovering-from-disaster-with-active-and-passive-project-server-and-backup-and-restore.adoc

@@ -10,4 +10,4 @@ If your active {ProjectServer} fails, activate your passive secondary server.
 . Switch DNS records of the active server with the DNS records of the passive server.
 This ensures that hosts remain connected and you do not need to re-register them.
 . Assess the functionality of your new active {ProjectServer}.
-For more information, see xref:Retrieving_the_Status_of_Services_{context}[].
+For more information, see xref:retrieving-the-status-of-services-by-using-web-ui[].

guides/common/modules/proc_recovering-from-disaster-with-active-and-passive-project-server-with-external-storage.adoc

@@ -14,4 +14,4 @@ This ensures that hosts remain connected and you do not need to re-register them
 . If your shared storage was mounted on both your active and passive servers, your passive server can already access the data.
 . If your shared storage was mounted only on your active server, re-mount it on your passive server.
 . Assess the functionality of your new active {ProjectServer}.
-For more information, see xref:Retrieving_the_Status_of_Services_{context}[].
+For more information, see xref:retrieving-the-status-of-services-by-using-web-ui[].

guides/common/modules/proc_retrieving-status-of-services.adoc → guides/common/modules/proc_retrieving-status-of-services-by-using-cli.adoc

@@ -1,18 +1,13 @@
 :_mod-docs-content-type: PROCEDURE
 
-[id="Retrieving_the_Status_of_Services_{context}"]
-= Retrieving the status of services
+[id="retrieving-the-status-of-services-by-using-cli"]
+= Retrieving the status of services by using Hammer CLI
 
+[role="_abstract"]
 {Project} uses a set of back-end services.
-When troubleshooting, you can check the status of {Project} services.
+When troubleshooting, you can check the status of {Project} services by using Hammer CLI.
 
 .Procedure
-* In the {ProjectWebUI}, navigate to *Administer* > *About*.
-** On the *Smart Proxies* tab, view the status of all {SmartProxies}.
-** On the *Compute Resources* tab, view the status of attached compute resource providers.
-** In the *Backend System Status* table, view the status of all back-end services.
-
-.CLI procedure
 * Get information from the database and {Project} services:
 +
 [options="nowrap", subs="+quotes,verbatim,attributes"]

guides/common/modules/proc_retrieving-status-of-services-by-using-web-ui.adoc

@@ -0,0 +1,15 @@
+:_mod-docs-content-type: PROCEDURE
+
+[id="retrieving-the-status-of-services-by-using-web-ui"]
+= Retrieving the status of services by using {ProjectWebUI}
+
+[role="_abstract"]
+{Project} uses a set of back-end services.
+When troubleshooting, you can check the status of {Project} services in {ProjectWebUI}.
+
+.Procedure
+* In the {ProjectWebUI}, navigate to *Administer* > *About*.
+** On the *{SmartProxies}* tab, view the status of all {SmartProxies}.
+** On the *Available Providers* tab, view the status of enabled compute resource providers.
+** On the *Compute Resources* tab, view the status of attached compute resource providers.
+** on the *Plugins* tab, view the list of installed plugins.