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 12 runnables are installed.
zoo_m : STARTED (com.aris.runnables.zookeeper-run-prod-1.0.0-RC22-
Trunk-SNAPSHOT)
postgres_m : STARTED (com.aris.runnables.PostgreSQL-run-prod-1.0.0-RC22-
Trunk-windows64-SNAPSHOT)
couchdb_m : STARTED (com.aris.runnables.couchdb-run-prod-1.1.1-RC22-Trunk-
windows-SNAPSHOT)
cloudsearch_m : STARTED (com.aris.cip.y-cloudsearch-run-prod-3.0.0-RC32-Trunk-
SNAPSHOT)
elastic_m : STARTED (com.aris.runnables.elasticsearch-run-prod-1.0.0-RC22-
Trunk-SNAPSHOT)
apiportalbundle_m : STARTED (com.aris.apiportalbundle.y-apiportalbundle-run
-prod-12.0.0-RC29-Trunk-SNAPSHOT)
loadbalancer_m : STARTED (com.aris.runnables.httpd.httpd-run-prod-1.0.0-RC22-
Trunk-windows64-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.
Contact Support
|
Community
|
Feedback