The order of stopping and starting the subsystems is important. Start and stop scripts are provided that take care of that for you for Edge components running on the same node.
Stop order: If you install Edge on multiple nodes, then you should stop Edge components on those nodes in the following order:
1. Apigee UI
2. Management Server
3. Router
4. Message Processor
5. Qpid Server
6. Postgres Server
7. OpenLDAP/ApacheDS
8. Qpidd
9. PostgreSQL
10. Cassandra
11. ZooKeeper
Start order: If you install Edge on multiple nodes, then you should start Edge components on those nodes in the following order:
1. ZooKeeper
2. Cassandra
3. OpenLDAP/ApacheDS
4. Qpidd
5. PostgresSQL
6. Management Server
7. Router
8. Message Processor
9. Qpid Server
10. Postgres Server
11. Apigee UI
The following scripts detect the Apigee components configured to run on the system on which the script is executed, and will start or stop only those components in the correct order for that node.
To stop Apigee Edge, Apache Cassandra, and Apache ZooKeeper: /opt/apigee4/bin/all-stop.sh
To start Apache ZooKeeper, Apache Cassandra, and Apigee Edge: /opt/apigee4/bin/all-start.sh
To check if the server is running: /opt/apigee4/bin/all-status.sh
For a detailed status check of the Apigee server, run the check.sh script: /opt/apigee4/bin/check.sh
Note: Now you can use options (command line parameters) to start and stop the individual servers.
Usage: ./all-st*.sh [ -d | -g | -a ]
-d | -- impacts only ZooKeeper and Cassandra
-g| -- impacts only Management Server, Message Processor, Router, LDAP, UI, Qpid Server, Qpidd, Postgres Server, and Postgresql
-a | --impacts all installed services (same as no parameter)
Starting, Stopping and Restarting an Individual Service
You can use the following tool to start/stop/restart an individual Apigee service on any specific server. The tool uses /opt/apigee4/etc/init.d/*, but adds logic, for example:
Perform a clean Cassandra shutdown on stop Uses wait-for-*.sh on start to check whether the component really started well. Usage: /opt/apigee4/bin/apigee-service <service> <command>
where:
<service> is one of the following: management-server, ui, router, message-processor, qpid-server, postgres-server, zookeeper, cassandra, apacheds, openldap, qpidd, postgresql <command> is one of the following: start, stop, restart For example, to only start or stop or restart Management Server, run the following commands:
apigee-service management-server start
apigee-service management-server stop
apigee-service management-server restart
You can also check the status of an individual Apigee service by using the following command:
apigee-service management-server status
LinkedIn
Twitter
