Verifying the Status of API Portal Components
Use the ACC to manually manage API Portal components. To monitor the status of all API Portal components (runnables), use the list command.
In the following example, the response from the list command shows the component apiportalbundle_m with a status of STARTED.
ACC+ localhost>list
On node localhost 7 runnables are installed.
zoo_m : STARTED (com.aris.runnables.zookeeper-run-prod-99.0.0.0-a-
_trunk-SNAPSHOT)
postgres_m : STARTED (com.aris.runnables.PostgreSQL-run-prod-99.0.0.0-a-
_trunk-SNAPSHOT)
cloudsearch_m : STARTED (com.aris.cip.y-cloudsearch-run-prod-99.0.0.0-a-
_trunk-SNAPSHOT)
elastic_m : STARTED (com.aris.runnables.elasticsearch-run-prod-99.0.0.0-a-
Trunk-SNAPSHOT)
kibana_m : STARTED (com.aris.runnables.kibana-run-prod-99.0.0.0-a-
Trunk-SNAPSHOT)
apiportalbundle_m : STARTED (com.aris.apiportalbundle.y-apiportalbundle-run
-prod-99.0.0.0-a-_trunk-SNAPSHOT)
loadbalancer_m : STARTED (com.aris.runnables.httpd.httpd-run-prod-99.0.0.0-a-
_trunk-SNAPSHOT)
For more details about the
API Portal components and their status in the ACC, see
API Portal Components and
Understanding
API Portal Component Status in ACC.