> [!CAUTION]
> **Caution:** This documentation covers Edge for Private Cloud 4.18.05, which is no longer supported. Google does not provide security patches, bug fixes, or technical support for this version. The current supported version is 4.54.00. See the [Edge for Private Cloud documentation](https://docs.apigee.com/private-cloud/latest/overview) for the current version, or [All versions](https://docs.apigee.com/private-cloud/versions) to compare releases.

*Edge for Private Cloud v4.18.05*

## Stop/start order

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 *stop order*:

1. Management Server (`edge-management-server`)
2. Message Processor (`edge-message-processor`)
3. Postgres Server (`edge-postgres-server`)
4. Qpid Server (`edge-qpid-server`)
5. Router (`edge-router`)
6. Edge UI (`edge-ui`)
7. Cassandra (`apigee-cassandra`)
8. OpenLDAP (`apigee-openldap`)
9. PostgreSQL database (`apigee-postgresql`)
10. Qpidd (`apigee-qpidd`)
11. ZooKeeper (`apigee-zookeeper`)

### Start order

If you install Edge on multiple nodes, then you should start Edge components on those nodes in
the following *start order*:

1. Cassandra (`apigee-cassandra`)
2. OpenLDAP (`apigee-openldap`)
3. PostgreSQL database (`apigee-postgresql`)
4. Qpidd (`apigee-qpidd`)
5. ZooKeeper (`apigee-zookeeper`)
6. Management Server (`edge-management-server`)
7. Message Processor (`edge-message-processor`)
8. Postgres Server (`edge-postgres-server`)
9. Qpid Server (`edge-qpid-server`)
10. Router (`edge-router`)
11. Edge UI (`edge-ui`)

## Start/stop/check all components

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 all Apigee components:

  ```
  /opt/apigee/apigee-service/bin/apigee-all stop
  ```
- To start all Apigee components:

  ```
  /opt/apigee/apigee-service/bin/apigee-all start
  ```
- To restart all Apigee components:

  ```
  /opt/apigee/apigee-service/bin/apigee-all restart
  ```
- To check which components are running:

  ```
  /opt/apigee/apigee-service/bin/apigee-all status
  ```

## Start/stop/restart individual components

You can use the `apigee-service` tool to start/stop/restart or check the status of
an individual Apigee component on any specific server.

```
/opt/apigee/apigee-service/bin/apigee-service component_name [start|stop|restart|status]
```

Where <var translate="no">component_name</var> identifies the component. Possible values of
<var translate="no">component_name</var> include (in alphabetical order):

- `apigee-cassandra` (Cassandra)
- `apigee-openldap` (OpenLDAP)
- `apigee-postgresql` (PostgreSQL database)
- `apigee-qpidd` (Qpidd)
- `apigee-sso` (Edge SSO)
- `apigee-zookeeper` (ZooKeeper)
- `edge-management-server` (Management Server)
- `edge-management-ui` (new Edge UI)
- `edge-message-processor` (Message Processor)
- `edge-postgres-server` (Postgres Server)
- `edge-qpid-server` (Qpid Server)
- `edge-router` (Edge Router)
- `edge-ui` (Classic UI)

For example, to start, stop, or restart the Management Server, run the following commands:

    /opt/apigee/apigee-service/bin/apigee-service edge-management-server start
    /opt/apigee/apigee-service/bin/apigee-service edge-management-server stop
    /opt/apigee/apigee-service/bin/apigee-service edge-management-server restart

You can also check the status of an individual Apigee component by using the following
command:

```
/opt/apigee/apigee-service/bin/apigee-service component_name status
```

For example:

```
/opt/apigee/apigee-service/bin/apigee-service edge-management-server status
```