The control framework

This guide assumes that you are using the Deployment Template with the Endeca Application Controller (EAC) as your primary control framework.

By now you know that the typical Endeca implementation involves many different components (such as CAS, Workbench, Forge, Dgidx, Dgraph) that can run on different physical servers. Each such server also hosts the EAC Agent or the EAC Central Server. In other words, the EAC is a control system that manages these components on each physical server for the Endeca implementation and coordinates communication between them.

The Deployment Template allows you to start and run the components through the Endeca Application Controller (EAC) as well as run baseline and partial updates.

The EAC is a mandatory component of the Endeca implementation, while the Deployment Template is optional and is used to communicate with the EAC. While you can use other methods to communicate with the EAC, the Deployment Template provides a convenient framework and a set of scripts that simplify these tasks and is the recommended method for managing your implementation.