Comparing standalone and operational Ambari server set up
Setting up a standalone Ambari Server instance is very similar to setting up an operational Ambari Server instance. Many of the steps are the same, with one key exception: you do not install a cluster using a standalone server instance. A standalone Ambari Server instance does not manage a cluster and does not deploy or communicate with Ambari Agents; instead, a standalone Ambari Server runs as web server instance, serving views for users.
The following table compares the high-level tasks required to set up an operational Ambari Server and a standalone Ambari server:
| Operational Ambari Server | Standalone Ambari Server | ||||
|---|---|---|---|---|---|
| 1 | Install ambari-server package | Install ambari-server package | |||
| 2 | Run ambari-server setup (DB, JDK) | Run ambari-server setup (DB, JDK)
|
|||
| 3 | Configure external LDAP authentication | Configure external LDAP authentication | |||
| 4 | Install cluster | Do not install cluster | |||
| 5 | Deploy views | Deploy views | |||
| 6 | Create and configure view instances | Create and configure view instances | |||
| 7 | (Optional) Repeat for each Ambari Server instance | ||||
| 8 | (Optional) Set up proxy for Ambari Server instances | ||||
| 9 |
(Optional) Set up SSL for Ambari |
