# Application Deployment

This section describes the application deployment tasks.

- Deployment prerequisites
  Before beginning application deployment, ensure that the Oracle Endeca components have been installed on all servers that will make up your deployment environment and that environment variables used by the Oracle Endeca software (including `ENDECA_ROOT`) are set.
- EAC applications
  In order to begin development, the template must be deployed onto the primary controller server in the deployment environment. Installation scripts have been provided for Windows and UNIX, relying on a common Perl installer to perform the deployment steps.
- Custom applications
  This section provides information about deploying custom applications.
- Usage and development
  Once installed, the Deployment Template includes all of the scripts and configuration files required to create an index and start a cluster of MDEX Engines.
- Displaying the Deployment Template version
  You can print out the version number of the Deployment Template from the command line.
- Configuring an application
  This section guides you through the process of configuring the deployment to run your application.
- Running the sample baseline update scripts
  Run the sample test scripts to create your first index and start the MDEX Engines in your deployment environment.
- Running the sample partial update scripts
  In addition to the baseline update scripts, the deployment template provides a set of sample partial update scripts.
- Communicating with SSL-enabled Oracle Endeca components
  The Deployment Template supports enabling SSL to communicate securely with the EAC Central Server and with the CAS Server for version 3.0.x and later. (Secure communication between the Deployment Template and the CAS Server is not supported in CAS 2.2.x.)
- Customizations
  The standard processing and script operations of the Deployment Template are sufficient to support the operational requirements of most projects. Some applications require customization to enable custom processing steps, script behavior, or even directory structure changes.